If nothing else the vendor-specific crappy toolchains do support the vendor’s HW well, so that’s something they need to do so that devs don’t have to start their projects with implementing the low-level support by themself.
693 karma · joined June 3, 2016
If nothing else the vendor-specific crappy toolchains do support the vendor’s HW well, so that’s something they need to do so that devs don’t have to start their projects with implementing the low-level support by themself.
If anything, we are starting to cross the threshold age of "plastics are everywhere" that I'd definitely expect some population-level effects starting to manifest in earnest.
Every year moves the microplastic scare towards the same slot that Electromagnetic hypersensitivity occupies in my mind. (Mind you that I'm not conflating the two yet, but every year we go without microplastic catastrophe moves the needle slowly into that direction.)
Looks very interesting, will definitely have to give this a deeper try.
Time to prompt everyone at $WORK to upgrade…
Does this vulnerability allow the attacker to compromise the original system where the user starts the agent-forwarded connection? Or ”only” compromise machines forward from the jump host?
A more cynical take would be to wonder if it has anything to do with their steps trying to monetize Docker Desktop. This move puts the same stack in use with Linux, maybe giving them monetization on Linux as well. (Not that there’s anything wrong with that. You can still use the Docker Engine freely on Linux if you want. )
[1] https://docs.docker.com/desktop/faqs/linuxfaqs/#why-does-doc...
We used to joke at my alma mater that the administrators were just trying to fill up their building to get a new one. The joke turned more than a little sour when it actually happened. And no, the university hadn't seen anything resembling necessary growth for such an explosion in administrative staff. If anything the faculties had been under cost-cutting for some years when it happened.
I think the phrase "you can't make this shit up" was coined for these situations...
One absolutely fantastic upside for just getting it done is that even if you have to redo it from scratch, you have so much better real-world understanding of the problem space.
I'm inclined to think that this applies to majority of the things we do, but is often brought up regarding building products in the idea that one should build the first prototype quickly, just to be scrapped so the final solution can be built from clean slate, benefiting from all the knowledge the prototype helped us gather.
Most often, in my experience at least, the knowledge one gains from actually doing the thing (even badly) surpasses anything that could have been gained with excessive planning. To actually work, genuine effort including some planning is definitely needed, but I don't think that's too high a bar. At least not when compared to the skills and knowledge one would have needed to achieve the same success with "just" excessive planning up front.
Flatpak I can see, but Wayland? I've been under the impression that X is going the way of the dodo in any case (maintainers becoming scarce etc.), and that Wayland has been (and is) the only real alternative that is being worked on.
Now, this is just my (very much non-expert) understanding on the matter, so if you have anything more substantial to add (or link me to) for further reading it would be much appreciated.
If so, what's your objection? To me this amounts to more or less just expanding the Redis ecosystem, which feels like a win-win.
I'm honestly asking in good faith, as the commits you gave as an example are literal anathema to me, and I'd like to understand what value anyone can see in them.
I'm honestly rather confused on the whole idea of valuing the journey instead of the end result. Aren't commit messages literally the built-in way to write about your journey to your heart's content? And failing that, you probably (should) have a ticket system or the like to preserve even more context in the form of third party comments etc.
I usually compare git history to a book: it's not valuable for the end user to see all the tiny edits and errors the author made before the final version, and in the end the important thing is that it tells a good story that the end user can easily follow.
Like it's said, the source code is for us humans to read. The computers would do just as fine without the story its trying to tell.
I think succeeding in this part already requires quite a bit of the understanding that Chesterton's Fence is actually calling for.
If you're (in good faith) able to make an informed opinion between choosing taking the risk and gathering yet more additional information, you're already in a much stronger position than what's usually considered as the failure mode of not taking the Fence into account at all.
Don't get me wrong, I'm all for advertising as a business model and it's awesome how advertising on the web has allowed at least some of the content creators on the web to monetize their valuable work. But I'm strongly against the idea that anything in that equation actually depends on the global spy network of the advertisers.
Nobody was complaining or refusing to use advertising to their benefit pre-internet, so why wouldn't the same non-privacy-destroying methods work just as well as previously?
Just for the sake of curiosity, what do you think it would take for your addon to be ported to work also on Android?
I think that would be even more important than the Private shortcut, with the amount of unnecessary crap the websites try to cram on your screen.
...but yes, it was also rather heavy on the eyes on my 4K display.
Overall, the whole piece gave me quite systems thinking vibes. For example, this part (well, and also the other 2 of the "three high-level features" the author lays out) towards the end:
> But in a more “Elvish” paradigm, however, the moment the house is built is not the end. How will this building grow? What other purposes will it satisfy in the future? When and how will it be deconstructed? What would happen with the earth on which it is built? All these “Elvish” questions[20] (and many more) can help develop a deeper understanding of both the problem and the solution spaces, and reframe (re-timeframe) both. The moment when the house is needed is not the end, but it is also not the beginning. How did the need for the house emerge? Where did the materials for it come from?
Edit:
actually, on second read this hits so close it's almost spooky:
> the relationship between action and understanding is more symmetrical: we act so that we can learn, as much as we learn so that we can act
I've lost the count how many times I've had the discussion in my organization lately about "starting the implementation already so that we can learn more, as currently we know less about the problem than we will ever know".
Granted, to maximize learning there must be some, usually non-trivial amount of effort at understanding and learning before the initial direction is sufficiently correct for the "act" part to provide actual learning and insight. But in my experience that's most of the time much easier to achieve than one would initially think. The amount of effort also tends to scale rather well with experience, so more experienced engineers are able to start acting into the broadly right direction with much smaller initial effort (which, in essence, is probably the definition of "experience").
Sounds interesting and rather extraordinary, would be great to read more on your thoughts on that. Do you refer to the Grapl blog?
Asymmetric cryptography with its Math Magic IS the solution industry came up with.
The problem with that is that you don't actually get that much benefits from the underlying microkernel. Linux is just the same old monolith, just better isolated from the other resources not exposed to this particular (para)virtualized kernel instance, so you end up isolating more or less complete systems from each other rather than getting the normal benefits of capability based microkernel architecture inside a single system.
Now that's not nothing of course, but not usually what people are after when they're hoping for a usable, modern microkernel system.
This kind of thing is quite big at the moment in mobile work machinery circles, everyone's looking for a certifiably safe solution for enabling mixed-fleet operation (i.e. humans, human-controlled machines and autonomous machines all working in same area). Current safety certifications don't view the nondeterminism of ML models too kindly.
Just like Linus for PC, I think it sensible to consider libc and other to be dynamically linked also on embedded systems, but maybe even less for other software.
I agree that the main appeal of HN is undoubtedly the community. There's no other place where you can be exposed to so many no-bullshit comments and submissions from so many people so deeply embedded in the industry.
However, I disagree that the design has nothing to do with it. I think the spartan design keeps the appeal of HN low for those who don't fully appreciate the value the community itself brings. Case in point, many people who post here are also probably on Twitter and/or Facebook. But Twitter and FB knowingly pursue such directions in their UI and UX and overall service design that having anything like HN on those platforms is all but impossible.