I think Andrew is a big part of it, and the people he surrounded himself with are the other part.
What kind of pre-1.0 language hosts conventions? Crazy that they manage to do that.
Andrew's vision has always been clear and inspiring to me. I think this got Zig its initial following, and they have capitalized extremely well on it to grow as a community.
How do you even warp these things? Had mine for 3y, sturdy as hell.
So sturdy in fact that the only piece I've had to replace is the charger, what's the point in swappable parts now right? /s
Kakoune has replaced many features with multicursor, including the sed-like commands (where you just select an area, search for patterns inside it to create the multiple cursors, then perform regular edits (which also means you can perform much more complex than simple replaces).
It is really useful for refactors, e.g. even if you don't have any LSP (e.g. for plain text) you can easily rename symbols, reorder/select in log files, etc
Rust has editions for strong stability guarantees, and has had them for nearly a decade i believe. Besides, tech backing has grown way past the risky point.
Who deserves to receive help (and, by contrast, who is undeserving of even basic decency) should never, ever be the decision of a few ploutocrats. The state should decide on such matters, and be the upholder of equality. Else, misery becomes a contest for who can be the most compelling, most attractive miserable to the elites.
> Oxide employees bear responsibility for the artifacts we create, whatever automation we might employ to create them.
Yes, allow the use of LLMs, encourage your employees to use them to move faster by rewarding "performance" regardless of risks, but make sure to place responsibility of failure upon them so that when it happens, the company culture should not be blamed.
No, that would be https://1000hv.seiya.me/en/
Easy mistake to make though, it is the 3rd such guide being posted in a week, definitely seems like the subject has a lot of traction.
Not all devs have very deep knowledge of the ecosystem, some will get to use a tool only if it's part of the default set of tools they're provided.
Plus, it saves on memorizing a name if you only use python once in a long while.
There just isn't much of a reason not to.
I fully expect that the intention is to force you into opening up the laptop to install the RAM. RAM is so easy to install that there's basically no risk of the customer messing up, and it exposes you to how easy it is to open up your laptop and how high quality the build is. Worked very well for me, I knew I would not accept buying anything of a lower standard before I even powered it on for the first time.
Shale oil is extremely unreliable, and its producers have barely ever been able to make any margins out of it because the required investments are heavy and constants. Wells reach maturity after months or weeks, and then they need to be replaced. If we have not yet reached peak all oils, then it will probably happen in the coming years.
Conventional has already peaked, and it is possible that even producers will decide to stop extracting nonconventional oil because it is too expensive and the price of a barrel fluctuates too much (IEA 2020)
Read it too, and I had a similar feeling. To me it was the thought that we will probably never see a place like Bell labs -a temple to knowledge, to gather great minds and let them work on whatever they think might have interesting outcomes, no matter how long it takes to obtain results and without having to worry about short-term financial issues.
Now researchers -in my country anyways- are forced into mostly researching ways to obtain funding and doing a little bit of actual research, almost as a side gig.
Except the strike is not really against LoL as a game, but as one of the largest clients of the actually targeted company.
The strike is purely an industry strike and does not have much to do with players, as it originates in the VA company trying to pull a scummy move to bypass an union.
The strike's goal was to force Riot to take position and disavow the company, which has been successful.
Not trusting the clients and redoing all calculations server-side would require massive processing on the server side.
Your idea then multiplies the load on the server.
The learning curve depends strongly on what you are trying to do.
Many things are very undocumented in Nix, and the interpreter being lazy creates very hard to read errors. No static typing makes everything worse.
If you are trying to configure your system using NixOS, the available options are very well documented so I personally rarely get into trouble.
Packaging an application however can be very difficult.
This just reminds me of my theory of Microsoft's checklist-driven development:
Some PM writes down some single-sentence description of a feature (e.g. "Share Wi-Fi passwords with contacts") and the developers just read the list and find the single least-effort way of implementing it.
Once done, they can tick the item off the list and go home having done their job, although often in the most excruciatingly stupid way by damaging their users' experience.
I do not see how else could M$ so often add features in a way that actively make their products worse to use.
Wasn't the recent liblzma attack already exploiting the fact that systemd has its hands in pretty much everything? Wouldn't this expand further the attack surface of systemd and the systems that connect with it?
Wasn't CPython supposed to remain very simple in its codebase, with the heavy optimization left for other implementations to tackle? I seem to remember hearing as much a few years back.