sacado2

12 ms·

91.
by sacado2 5y ago
This is probably a bit overkill for that kind of problems. In Anaconda, the problem is probably that the instance isn't described optimally. In real life (that is, unless you make it up and artificially find the worse possible example)
92.
by sacado2 5y ago
Yes, because the examples you give already have a solid reputation. You can get away with it when you are "the government .gov", but if you are "small start-up.com" and I want to invest in your risky stocks and all I get
93.
by sacado2 6y ago
A huge, 2-decades gap. Way too late, because in the meantime, Turbo Pascal had been developed and made the language practical (and btw I'm still impressed by the quality of TP's "IDE" for the time), and in 1990 you had s
94.
by sacado2 6y ago
But then ISO Pascal is not 50 years old, far from it. The Pascal from 50 years ago was not that great in practice.
95.
by sacado2 6y ago
Go is starting to get a bit old though. Version 1.0 dates back from 2012, 9 years ago. It's as old and mature as Java was in 2005.
96.
by sacado2 6y ago
Even better, in practice we have amazing tools nowadays that can solve practical NP complete problems in a reasonable amount of time (I mean, optimal solutions, not OK-ish ones).
97.
by sacado2 6y ago
It's all about technique and the style you want to develop. Two singers can have very different voices too.
98.
by sacado2 6y ago
Last time I used NPM, it tended to download megabytes of dependencies for each project . If you used a package in, say, 10 different projects, you had 10 copies of it. Did they solve that issue?
99.
by sacado2 6y ago
> I think enabling a language to be garbage collected in general, while making a borrow checker opt in for special, time critical functions is the best of both worlds. Put everything you don't want to manage into Rcs, RefCells, Boxe
100.
by sacado2 6y ago
Yes. I think Zig is a safer C, while Rust is a safer C++. C programmers will be more excited by Zig than by rust, and the opposite is true for C++ afficionados.
101.
by sacado2 6y ago
The problem is, you can't know in advance whether a given piece of code will ever need to grow in the future or not. I've seen way too many "one-off POC prototypes" eventually be used in production because they did the j
102.
by sacado2 6y ago
The soft I have the most performance issues are Firefox, LibreOffice and Aperçu (don't know its original name, but it's called that way in French -- Apple's PDF viewer). All of them written in different, non-GCed languages. U
103.
by sacado2 6y ago
It reminds me of the good old C++ times, when people were scared OOP would make their programs unacceptably slow because of virtual functions. That's why methods are not "virtual" by default, which led to nasty bugs when you
104.
by sacado2 6y ago
But there's a cost induced with this superior productivity, and it's not only about speed. Maintaining and updating these (dynamically typed) programs in the future feels way less productive because things start to break everywher
105.
by sacado2 6y ago
> Then how come everything is so ridiculously slow these days, despite faster computers? As you said, it's usually not a GC issue. Many of these ridiculously slow programs you talk about are written in C++.
106.
by sacado2 6y ago
Don't forget good old Ada.
107.
by sacado2 6y ago
Why don't you write a book called "rust gotchas: 4000 subtle ways rust can try to f*ck up with you and how you can defeat it"? I'm (almost) serious (if you do that, do several, specific titles: "100 lifetime gotchas
108.
by sacado2 6y ago
> 2) Started getting good consulting projects 3) Started getting Royalties(Passive income) Yes, I think technical books are a great marketing asset when you're a consultant / freelancer. It gives you a ton of credibility, more
109.
by sacado2 6y ago
Thank you! I didn't know about the `=n` syntax.
110.
by sacado2 6y ago
The worse bug I fought in one of my rust programs was when using the range type. I needed to go from n to 1 included, so, from n included to 0 excluded. Of course `(n..0)` didn't work, so I tried `(0..n).rev()`, which didn't work
111.
by sacado2 6y ago
Are we talking about semver in general or semver the way it is (supposed to be) used in go mod?
112.
by sacado2 6y ago
I'd be glad to be presented a real-world counter-example in a (non-toy) go library.
113.
by sacado2 6y ago
> Just what is a breaking change anyway? It's just an API kind of thing. If a function / constant / var / type was available and is not anymore, it's a breaking change. It's an objective measure, there is no
114.
by sacado2 6y ago
> ADA has proper arrays, with bounds checks. Not only that, but you can also opt out at compile-time if you need, for performance reasons. You also have (optional) runtime bound-checking for scalar values (aka "integers"), and
115.
by sacado2 6y ago
It's a well known psychological phenomenon though. Losing a given sum of money is more painful than earning that same amount. if you find a $20 banknote on the sidewalk, you wont be as happy as the guy who lost lost it is pissed off.
116.
by sacado2 6y ago
> The fact that they use the same compiler is to me a devastating argument. GCC can also compile Ada. Would you say C/C++/Ada is a single language?
117.
by sacado2 6y ago
Are they going to make non-backward-compatible changes, or is this just a marketing move?
118.
by sacado2 6y ago
I learned programming before I learned English. I was always confused by PRINT vs INPUT: which one reads and which one writes? So yeah, it could have been grob and bolver or anything.
119.
by sacado2 6y ago
A C++ function declaring several uninitialized pointers one after the other is very suspicious anyway. It looks like the programmer is trying to write old-school (pre C99) C code (declaring all variables at the top of the function) in C++.
120.
by sacado2 6y ago
I think it's the first time I see someone call Go a modern/innovating/fast evloving language. What attracted me to this language in the first place is the fact backward compatibility is seen as a dogma in the community. It&#x

More ›