2,343 karma · joined September 18, 2013
then Yantra would become great to parse well-known structured data from python at low-level speed.
this is extra helpful if the parser generator also generates intuitive language bindings to, e.g. python or TS.
when systems engineers through intelligent restructuring of low level data structures save 1 TB of ram for their company without loss of productivity that is unrelated to revenue and market but still improving the bottom line.
if FB puts strings shorter than 64 bytes not on the heap but into the string control data via a union, that's in the same category of saving costs without adding a single new feature.
so much fun, thanks a ton!
mobilitY for parents with little children or people in wheelchairs was "not a priority"
it's not that NYC subway was a novelty isn't it?
I then realized "accessibility" translates straight to: mobility with little children. which affects many many additional people, but it's rarely in the public discourse anywhere.
in Paris in 2019 I then saw parents with tiny light-weight sit-on micro scooters, as a creative work-around to the parental public mobility challenge.
but 2055? ooof.
I have high hopes for a positive social impact of self-driving cars out there.
alas, only GPL-3 gives the right to repair and modify the TV or car or refrigerator you own...
the trend to give software mit or bsd licenses instead ead of GPL is concerning.
mind to share sources to that part? that's saying "Nazi" btw.
correct is that he was a conservative engineer who happened to be intelligent and live in that era, and who was lucky enough to work in his domain instead of dying a cannon fodder somewhere. did they build weapons? sure thing. does that make him a convinced fascist? certainly not.
he wasn't even member of the NSDAP party.
here is a short biography based off complete archive material:
Deutsche Biographie - Zuse, Konrad https://www.deutsche-biographie.de/gnd118637436.html
we'll know more after the midterms.
they're the single most important elections the US had in the past decades. good luck to all of us!
but I digress.
it's not that simple to "just say no".
only now I realize I misread your comment as saying "besides tree sitter and eglot there is not much in emacs"
and somehow that is not what you said.
is this what you meant: "Now that modern IDE features (syntax parsing and LSP support) are built into Emacs out of the box, I don't feel like I'm missing out on modern editors like Zed. I’m ditching my bloated, outdated Emacs configuration file and starting fresh with a clean, lightweight setup that relies on standard built-in tools."
?
then apologies for my confusion.
fittingly so but still annoying. srry
an active project indeed!
actually it is very explicitly pushing to refactor and rejuvenate the working field tested code, instead of green field rewriting it.
elsewhere he goes on to what's needed for that, also see the great both entertaining and informative fosdem talks about rejuvenating LibreOffice
but no trash talk, no swear words, nothing gross or offending.
I was very much surprised and asked. give me demerits for the way of asking.
but the question stays: how come an encryption scheme inflates data by this order of magnitude and needs GB sized keys?
where can I learn about this? not the nutty gritty details proofs and all but an overview. assume I did my CS masters in the 1990s and worked as SW eng ever since.
NVM, I asked Gemini
> I read David Nicholas Williams's short blog post titled It's not empowering to hand off the details, in which he argues that AI cannot replace expertise because doing good work requires deep familiarity with the details.
> I couldn't agree more!
> He articulates very well the puzzling phenomenon I see every day with "AI-pilled" colleagues (including many engineers) who trust the model with far more than they should. They delegate the thinking and designing along with the execution, lose touch with the codebase, miss out on critical learnings, and then complain when the slop they produced doesn't solve the original problem.
> But I think the argument is incomplete without a counterexample. There is one phase where handing off work to AI is genuinely empowering, and that is worth defining and formalizing.