atilaneves

11 ms·

61.
by atilaneves 7y ago
> Programming languages don't make people miserable. Try coding in MUMPS then saying that again. Or Intercal. Or Whitespace.
62.
by atilaneves 7y ago
> Surely you are kidding. If that were true, why doesn't OCaml curb-stomp C in benchmarks? Exactly because nobody (except backend writers) can predict what C compiler backends emit, especially when abusing undefined behaviour.
63.
by atilaneves 7y ago
> you can get some very good performance Compared to... ? > I appreciate golang's simplicity when I need to review other people's code or dig into third party libraries. See, I don't. Every for loop has to be inspected
64.
by atilaneves 7y ago
> Go occupies the same niche as Python, Ruby and JavaScript (server-side business logic) Is this in a world in which Java and C# never happened?? > Compared to programs in those languages, Go programs are insanely efficient. In other
65.
by atilaneves 7y ago
> but as soon as you enter a physics-institution anywhere in the world, FORTRAN likely reigns supreme Not at CERN, but it used to be the case. It's C++ now. > It turns out that FORTRAN is a very good match for the way physicists
66.
by atilaneves 7y ago
These situations exist and in those, something like Rust is a very good idea. I maintain that these situations are far rarer than most people imagine (and I've had to deal with more than a few).
67.
by atilaneves 7y ago
This depends on the language. The one with GC I know best, D, would reallocate l2 when pushing to it so l1 wouldn't be modified.
68.
by atilaneves 7y ago
> Rust protects you from a whole class of shared-mutable-state issues Rust is not alone in this. I think Pony is a good example.
69.
by atilaneves 7y ago
> it just lets you do it in a more performant way. That's not necessarily true. It lets you do it without a tracing GC, which is marketing genius. Whether or not it's more performant depends. A lot. > It enforces rules aroun
70.
by atilaneves 7y ago
> it's the underscore insensitivity that makes it difficult to use standard search tools. I personally don't like the feature, but what do you find difficult about using /my_?[vV]ariable/ to search for any of myvariab
71.
by atilaneves 7y ago
> In Rust, I can be 100% confident that I will not have memory-unsafe code. Not 98%-and-I’d-better-check-those-last-2%-really-closely. One hundred percent. That’s a game-changer. Also achievable, and far more easily, with a tracing GC. D
72.
by atilaneves 7y ago
Been working 100% remotely for 3 years now. My biggest fear is having to go back to an office at some point in my career. I hope it never happens.
73.
by atilaneves 7y ago
I'm not exactly averse to templates... https://atilaoncode.blog/2015/02/11/the-craziest-code-i-ever...
74.
by atilaneves 7y ago
You'd be surprised...
75.
by atilaneves 7y ago
> Would be quite the project though, to port a fundamentally-compiled ecosystem like D to use an interpreter. Sort of. We already have an interpreter (CTFE!), it's just not up to the task for what I want to do with it.
76.
by atilaneves 7y ago
It's already possible to use D with Jupyter, but an interpreter will make it a lot faster.
77.
by atilaneves 7y ago
Part of my new job is trying to motivate people to do their best work. I'm still figuring it out.
78.
by atilaneves 7y ago
> Is this planned to be implemented Yes. > any hurdles and/or benefits in relation to your Vision? Hurdles: implementation issues, figuring out later on that there are ways to corrupt memory despite the rules we come up with. Ben
79.
by atilaneves 7y ago
Copy constructors were needed due to type checking const/immutable copying. C++ interop was just icing on the cake.
80.
by atilaneves 7y ago
You could share D .di files, which are akin to C/C++ headers, but automatically generated by the compiler.
81.
by atilaneves 7y ago
I'm working on a library right now that, I hope, will have an easy to use API. It'll also have a "mixin/ctfe version", whereby all reflected characteristics are returned as strings that can be mixed in. This opens t
82.
by atilaneves 7y ago
I didn't submit the link but I did write the blog post. AMA!
83.
by atilaneves 7y ago
So... remote work?
84.
by atilaneves 7y ago
I went back to C++14 a few years ago after writing D and it was painful. The only addition to C++17 that made my life easier was `void_t`, but even then it's not even close. Having to deal with headers again and C++'s templates wa
85.
by atilaneves 7y ago
Some people who don't like the skin peel them. I don't bother. The seeds likewise aren't a problem for me at all.
86.
by atilaneves 7y ago
> Rust tuples are delightful to use and C++ tuples are a monstrosity They're not great, but they're a lot better than using out parameters!
87.
by atilaneves 7y ago
How are guavas hard to eat raw??? I've literally lost count of how many guavas I've eaten.
88.
by atilaneves 7y ago
CERN has sheep on the site because it's the cheapest way to get the grass cut. It was weird having meetings that were punctuated by "baaah!" every now and again.
89.
by atilaneves 7y ago
> There are standard C libraries that handle strings very well. I'm not aware of any. I've never encountered a language that is more frustrating than C to manipulate strings in. > Are you saying other languages don't ha
90.
by atilaneves 7y ago
Everybody's brain works differently. Maybe C is the language for you. Maybe your tradeoffs are different from mine and you're ok with dealing with segfaults and security exploits. AFAIC if I never again have to write string handli

More ›