nickmonad

86 karmajoined 7 tahun yang lalu

https://nickmonad.blog/

comments

kemarindiscuss

Zig still offers a lot of great additions that make systems work more reliable. Optionals and comptime are two helpful things C does not have, and there are plenty others. One of their core devs addressed this in a thread over on Lobsters [1]

> Bounds checks, checked arithmetic, strongly-typed alignment, strongly-typed error codes, tagged unions, explicit undefined are some rather important language features. If Zig didn't exist, TigerBeetle would probably have been written in C, and the safety gap between C and Zig is just gigantic. And safety is one aspect of the language, Zig has a lot of going on for it elsewhere!

[1] https://lobste.rs/s/6rkdik/rewriting_bun_rust#c_8gebpa

kemarin duludiscuss

He's not.

> "There's a dichotomy being presented here where you have to either choose a "style guide" or a programming language feature in order to avoid bugs. The sleight of hand misdirects the reader away from the main way bugs are eliminated: by dedicating engineering resources to it. You're not giving TigerBeetle nearly enough credit. Quite simply they put in the time to find and eliminate the bugs, they make an effort to maintain a healthy relationship with ZSF, and Bun did not do that."

The reference to TigerBeetle is important, and a bit under-explained for the point he's trying to make. They have consistently attributed things like design and deterministic simulation testing to their success and reliability, which has nothing to do with Zig as a language. Some things might be _easier_ in Zig, such as static memory allocation, but ultimately, a holistic approach brings success, not one individual tool used "right".

16 hari yang laludiscuss

Andrew doesn't strike me as someone who does any marketing at all. He just wants to make the language he wants to use, and does it well.

Sometimes its just right time, right place. But also, Zig has received attention via projects like Ghostty, TigerBeetle, and Bun (prior to rewrite of course)

bulan laludiscuss

Yep. He mentioned recently in his JetBrains interview he wants Zig to be a language for the next 50 years. Rushing 1.0 for the sake of signaling to the wider industry today would be actively harmful to that goal.

2 bulan yang laludiscuss

Yeah or anybody who can still actually read code.

3 bulan yang laludiscuss

Sure. I'm just saying in the context where fully-managed SaaS was already decided not to be an option, and a customer is deploying vendor code in their environments, the update mechanism can in fact be a problem. It's not just poor CISO management.

3 bulan yang laludiscuss

I agree that keeping things up to date is a good practice, and it would be nice if enterprise CISOs would get on board with that. One challenge we've seen is that other aspects of the business don't want things to be updated automatically, in the same way a fully-managed SaaS would be. This is especially true if the product sits in a revenue generation stream. We deal with "customer XYZ is going to update to version 23 next Tuesday at 6pm eastern" all the time.

3 bulan yang laludiscuss

> So you're stuck debugging a system you don't control, through screenshots and copy-pasted logs on a Zoom call.

This is very real.

I work with a deployment that operates in this fashion. Although unfortunately, we can't maintain _any_ connection back to our servers. Pull or push, doesn't matter.

The goal right now is to build out tooling to export logs and telemetry data from an environment, such that a customer could trigger that export on our request, or (ideally) as part of the support ticketing process. Then our engineers can analyze async. This can be a ton of data though, so we're trying to figure out what to compress and how. We also have the challenge of figuring out how to scrub logs of any potentially sensitive information. Even IDs, file names, etc that only matter to customers.

3 bulan yang laludiscuss

On the streaming side, are you looking for Change Data Capture?

https://docs.tigerbeetle.com/operating/cdc/

3 bulan yang laludiscuss

Did you try asking the model?

4 bulan yang laludiscuss

Spam bots.

4 bulan yang laludiscuss

> It's a type of team building, improves employee morale and humanizes management. All lead to improved productivity in the long term.

Yes, but the important distinction is that its intention is to bring people together face-to-face, not isolate them to their desks for continued work. Just because the end goal is "productivity" broadly speaking, doesn't mean the mechanisms are socially/morally equivalent.

> I doubt anyone is forcing the employees to take the stimulants.

I agree, and I hope my comment didn't imply I thought that was the case.

4 bulan yang laludiscuss

I agree to a point. Although, alcohol (when consumed responsibly) has a social element to it, so companies having a "beers on Friday after 4pm" just feels different than "here's nicotine so you can be more productive and make us more money." They are serving different functions.

5 bulan yang laludiscuss

Not allowed.

5 bulan yang laludiscuss

Yeah definitely something that would've been posted as a joke in a "HN front-page 10 years from now" kind of thing.

5 bulan yang laludiscuss

You turn it on, and it scales right up.

5 bulan yang laludiscuss

Unless you're doing OLTP. Then, TigerBeetle ;)

6 bulan yang laludiscuss

https://nickmonad.blog/

Trying to blog more frequently with shorter posts!

6 bulan yang laludiscuss

Narrowing in on background color is an extreme oversimplification of what Tailwind provides. I found it to be a great tool for working with CSS, especially for layout. Business viability can be debated, but the value is way beyond what you suggested.

6 bulan yang laludiscuss

I agree with the sentiment that companies should help fund open source they depend on, but I think it's a stretch to say those business succeeded "only" because of Tailwind. It's a great project, although I'm pretty sure they would have figured out a way to work with CSS without it.