(Arguably solar/battery has the same problem as oil: let's dig and refine stuff from the ground, and not care about how to take care of the concentrated product once we're done with it. But to a much lesser extent.)
1,472 karma · joined July 14, 2021
https://www.linkedin.com/in/tommiegannert/
https://github.com/tommie/
https://tommie.github.io/
(Arguably solar/battery has the same problem as oil: let's dig and refine stuff from the ground, and not care about how to take care of the concentrated product once we're done with it. But to a much lesser extent.)
// Also handle case where target is a `Dynamic` shared value
// (returned by a variable resolver, for example)
Couldn't find any other information about a GC, so guessing this is pure ref-counting. Speaking of potential memory leaks, there's also string interning happening. I agree this seems to be for short-lived contexts right now.The Cullen observation that the OTP power supply wasn't being glitch detected was pretty damning and a much more devastating attack in practice. If you require decapping and lasers, anything is possible.
Thanks for the write-up!
So if you use this PCR state machine, the problem is that the step before initrd doesn't require the correct password to move the PCR forward? It accepts any password that decrypts the next stage, which didn't have its integrity verified here.
Seems there are multiple ways of solving this, and adding integrity checks is only one. It could also let the TPM verify the disk decryption password (when it's needed.)
This feels like one of those half-security measures that makes it feel like you're safe, but it's mostly marketing, making you believe *this* device can be both safe and easy to use.
I care a great deal about DevEx, and since no one else tends to care as much as I do, I can do good work for a few years, but then I'm worn out from fighting alone. I move on and hope things are more aligned somewhere else. Doesn't mean my co-workers are wrong for "not caring", just that I haven't found my peers.
The driver who doesn't let you into her lane perhaps cares deeply about not being late, again, to pick up her kids from daycare. Or her brother is about to do that stupid thing again, and if she doesn't try to stop him, she'll feel bad forever, again. Which lane you're in doesn't even register on her list.
Your argument became: By adding delimiters, even Python can play well with other languages. /s
In that case, it sounds more like a news agency.
This is the problem with experts and politicians. You can make money on either position, but once you have started stating your opinion, it's unlikely you'll do active research to disprove your opinion, as many have already concluded [1].
I'm happy that Simon only sees this as a hobby.
Anyone have data on layer adhesion?
(I have a spool of Royal Blue Prusament that has the worst layer adhesion ever, for some reason. Fresh in my mind. :)
In the 90s, we had shareware/freeware/beerware. No one expected source availability. At universities, the Unix world had open source, in the real sense. Then something happened that caused these two tracks to merge.
Maybe the university students grew up and carried on their belief in open source, but also had to create the business. After 20 years, they realized (1) it doesn't have to be open source to _feel right_ and (2) maintaining in the open is more expensive. They're now in management positions, not coding. Selling B2B doesn't require code to be open to the public, since you can have source available licenses. And as you said, perhaps ScyllaDB isn't really targeting the hobbyist. We'll continue this trend.
Or perhaps open source has stopped being a buzzword. We're now much more of a SaaS world, where being open source isn't as important as costing $10 per month or having 200 "data partners" that need to track you.
That said, I think there's a really good reason for core libraries and security-sensitive libraries to be open. I want to be able to inspect them, before using them. And I'm in the HN crowd of actually using open source code because I can fix bugs as I encounter them, but I realize this is a small crowd.
I'd love for open source to be a useful word again, and not something that goes on the Silicon Valley PR budget.
I think the concern that we won't have senior developers later if there are no junior developers now, is pretty valid. The question is if LLMs will keep up pace to replace senior developers when the current ones retire. Since no one can predict the future, it's a pretty risky gamble at the scale of the entire industry. (OTOH if this new tool sparks more interest in the occupation, then maybe the issue solves itself by sheer numbers.)
Seems they've entered some kind of reverse Minority Report middle ground, where they don't have to prove you committed a crime. If there is reasonable suspicion that a crime was committed for you to own that Rolex, it's gone. Possibly that means "you couldn't prove it was acquired legally."
There goes any chance of me returning to Sweden, I guess. This is going downhill fast.
[1] (Swedish) https://www.riksdagen.se/sv/dokument-och-lagar/dokument/sven...
> Bzlmod, the new way to manage external dependencies, is turned on by default since Bazel 7.0.
> We are aiming to remove WORKSPACE in Bazel 9 completely.
Oh, that's good to know. Sorry I wasn't paying attention, M.
At the same time, you must have been questioning whether you were staying informed, or was used as a democracy puppet by lobbyists. It takes a lot more energy to stay informed than to just read news.
Here in Switzerland, the people vote on lots of things, four times a year. But the participation rates are always 40-60%. It's almost like people only need to stay informed about the particular questions they care about. I find it a refreshing organisation, compared to my native Sweden. When I only vote for politicians, I need to know their opinions on everything. That, I find, is exhausting.
I saw something similar with wasm3, a project explicitly said to be in maintenance mode, because the maintainer is in the Ukraine and being busy with other stuff... I managed to triage and provide patches to some of them. The poster was doing fuzz testing by randomly generating WASM binaries. Once a crash was found, they just uploaded the binary as-was, with error message. Completely valid reports, but bad execution with context in mind.
This resulted in huge WASM binaries that could be reduced from thousands of instructions to ten with work. (Even that reduction could probably have been automated, which annoys me even more.) There were also duplicates because they posted 5-10 reports simultaneously, many with the same cause. This is something I feel they should have done ahead of posting.
> DO NOT submit reports that haven't been reviewed BY A HUMAN. This reviewing time should be paid first by you, not open source volunteers.
This seems like the most important point. LLMs are great for generating things. By all means, continue using them. Sometimes useful, sometimes not. It can be inspiring if used right. They are pattern matchers after all, and bug hunting is partially about finding patterns. However, GIGO, and they need a filter after.
(If you like using a hammer to fix dents in my car, don't say you're done just because you've had a few blows; tell me it's done when the dents are gone.)
I had the impression NaCL was about being highly opinionated, so this choice surprised me.
However, the benefit of automatic formatters is that if you really like 80 better, you can reformat before editing, and undo that before sharing your results.
E.g. test_activation_stats_functions [1] that just checks that the returned value is a float, and that it can take random numbers as input.
test_get_state_dict_custom_unwrap [2] is probably supposed to check that custom_unwrap is invoked, but since it doesn't either record being called, or transform its input, the assertions can't actually check that it was called.
[1] https://github.com/huggingface/pytorch-image-models/pull/233...
[2] https://github.com/huggingface/pytorch-image-models/pull/233...