2,097 karma · joined April 9, 2009
I really like the R tooling. What do you find clumsy about it?
It feels like the reason it’s popular is mostly just people not wanting to update skills
I have the opposite view. I find its the people who complain about R because its a bit different are the ones who are inflexible about learning new skills.
It turns out I didn't really need them and that I had not understood the lints correctly.
I recommend anyone else who is also skeptical to try to remove some of the disable comments -- you might be surprised.
I have the habit of writing notes in Markdown anyway and, with minor modifications, markmap will visualize it.
There is also a plugin for VSCode: https://marketplace.visualstudio.com/items?itemName=gera2ld....
I think the advantage with Hetzner cloud is that you rent the IP address separately. If you get an IP with a bad reputation you can stop renting it and get a new one.
Edit: I have not actually tried changing the IP, its just an idea. Also, I hope the spammers don't start doing this and spoil it for everyone else.
I've not had problems with Hetzner and Scaleway. Before that I used to host email on random vendors I saw on Low End Box[1] and never had problems.
There are a few strange comments about Germany in this thread.
Is there some internet movement whose pastime it is to make Germany look backward? What do you get out of it?
For instance: 'fd .apk' to search for android builds.
I think that this is only true for some projects. For some people, the ease of self hosted setup (one executable) and the fact that you can change the documentation, edit code and close bugs offline is a big win that no centralized service can compete with.
Any interesting code involves custom classes written by less experienced developers that are only used once or twice in an application -- it is there that that the complexity of destructors hurt.
... until you have to write a class yourself. Then you have to think of the complexities introduced by destructors such as copy semantics, move semantics and the destructors themselves.
You also have to deal with architectural questions such as should my file have a close method (C++) or do I always leave this to the destructor (Rust).
If I was to give an opinionated summary, a little complexity at the call site has been moved to a lot of complexity in the class implementation. Since there is, on average, one class implementation to many object uses, destructors might be considered a win. But I don't feel so strongly about it that I wouldn't consider a language for not having destructors.
The Amazon version has the nickname 'despair closet' [1].
[1] https://thehill.com/changing-america/well-being/mental-healt...
The 70s looks at your example of progress, thinks of it as a big ARPANET and is not impressed.
[1] https://github.com/rust-lang/packed_simd/blob/master/rust-to...
[2] https://crates.io/crates/packed_simd_2/reverse_dependencies
https://registry.terraform.io/providers/scaleway/scaleway/la...
C++ has supported units, as a library, since the early 90s. The Barton Nackman book had the initial implementation [1] and it was picked up years later by Scott Meyers [2].
[1] https://www.thriftbooks.com/w/scientific-and-engineering-c-a...
[2] https://stackoverflow.com/questions/28698558/c-dimensional-a...
But that's not the point. People aren't suggesting micro managing memory. Java has a well deserved reputation of being a memory hog and its using 20x what is needed in this benchmark.
I would stick with HN and live with the downvotes. It also helps to make any criticism polite.
I am not sure if it is idiomatic but I have been following the guidelines int this article for general error handling:
https://nick.groenen.me/posts/rust-error-handling/
And this article for having context:
You can vendor the dependencies you use [1].
[1] https://golang.org/ref/mod#go-mod-vendor
Its also worth noting that, since crates.io uses github for both authentication and hosting the index, the Rust ecosystem would also be effected if github goes down.
I hope their pay reflects that and is 3x the average.
The only downside of this technique is that people become less likely to collaborate or help you -- but who needs help when you have great techniques like this to fall back on?
One minimal Docker option with Go is to use a "distroless" Docker image: https://github.com/GoogleContainerTools/distroless/blob/main...
The opposite is also true. Many things we thought would be possible are either economically or technologically out of our grasp:
- Nitrogen fixation in wheat.
- A computer simulation of the catalyst that fixes Nitrogen in plants.
- Fusion power stations.
- Room temperature super-conductors
Maybe its possible to point to research that is almost there in most of these areas -- just like the 1950s.
Do you use rsync [1]? I ask because most of my collegues don't and they take minutes to deploy what I usually do in seconds.