- The office has no windows. That's a pretty sad working place :-(
- more or less my experience too. But I'd like it to succeed. Fortran is now the COBOL of science. I'll continue to follow it closely.
- I think it is way to slow too. The one from microsoft (pylance IIRC) is better in my opinion.
- It's been long since I've heard of Julia. It seems it has hard times picking up steam... Any news ? (yeah, I check the releases and the juliabloggers site)
- didn't find any video so: https://www.youtube.com/watch?v=sRL_RU7-jfc
- When I'm tired my typing goes bad. I obvioulsy meant: "is that number even odd ?" :-)
- Lots of network engineer don't understand the usefulness of a stack trace.
IOW: when my network fails "No route to host", I want to know who failed and why. Not just "hey, start the route tool on your production sever which you don't have access to, to get to know who slipped"
- I'm disappointed, it's not in rust. :-)
- With a tree you'll be limited by the RAM. I advise to use a database.
- Gemini took 4 seconds to answer this prompt: "Here is a number 4200020010101. Think deeply about it and tell me if it is not or or not even."
So if you're concerned with privacy issues, you can run the assembly version proposed in the article locally and be well within the same order of performance.
Let's thank the author of the article for providing a decent alternative to Google.
ah, but the license is not that good we can't reproduce his code.
- really good 1st of April joke !!! rotfl
ahem... We're not the 1st of April...
- It's not that it cannot, it just doesn't want to :-) (but you're right). I guess that in this very case of DLL, it's a bit hard to swallow. To be honest, it's because the rest of rust really helps me in other areas of my projects that I have accepted that. Learning the ownership model of rust is really painful, it really forces you to code in its way and it was not pleasant to me.
- it just may be: https://www.systemiq.earth/reports/invisible-ingredients/
- it is not straightforward in rust because the linked list is inherently tricky to implement correctly. Rust makes that very apparent (and, yeah, a bit too apparent).
I know, a linked list is not exactly super complex and rust makes that a bit tough. But the realisation one must have is this: building a linked list will break some key assumptions about memory safety, so trying to force that into rust is just not gonna make it.
Problem is I guess that for several of us, we have forgotten about memory safety and it's a bit painful to have that remembered to us by a compiler :-)
- Last day I asked Claude to estimate a loop of a dozen 6502 instructions. It failed but his estimate was not bad at all. Amazing!
- The Food Recipe example link doesn't go to a food recipe :-(
- I'm 53, started at 10. At that time, being able to edit a line of code without re-typing it completely was "cool" :-) Then, on apple 2, we had GPLE (global program line editor) then Assembler toolkit which had an editor. Then I moved to PC. First I used GWBasic (it had an editor) then Turbo Pascal, then multi-edit, then emacs, then Visual Studio, then Eclipse, then Word (became a manager :-)), then back to emacs and VSCode (coding again!) and a bit of Kate.
- yeah, typed too fast. I was talking about 40 years ago. Apple 2+ to be specific.
- I'm talking about things that were long before DOS even existed.
At that time you didn't even have the tools to cut sprites from image in the first place. That's why it took a lot of time (and I was 12 years old and my dad was pretty far away from an engineer, that didn't help).
One hundred kilometers from there, there is this station: https://en.wikipedia.org/wiki/Li%C3%A8ge-Guillemins_railway_...
by the same architect, and budget exploded as well...
So either local governments or Calatrava is messing around :-/