I don't think we did learn anything about modularization in the past 20 years. Programming languages still don't do it even remotely decently. Users still make a common mistake of splitting things into multiple files for the sake of splitting, just as your comment implies. These things are all about UX, which is known to be neglected in programming.
This is merely an example server with a router, middleware and two route handlers. This isn’t evangelism for monolithic application design, and there’s nothing inherent in Go that forces monolithic application design.
"Putting everything in one binary" is what we learned in the past 20 years. Most major languages either compile to a single artifact or they have some "bundling" trick to minimize runtime dependencies. Besides that, there are things like Docker which exist to solve the same problem.
Wouldnt 'they' have evolved 1000 yrs as well? By that time their own current state of evolution would look even less developed given the exponentiality of evolution.
Perhaps we just need to stop being dangerous to other species and ourselves. Embracing the pursuit of collective goals would be a huge advance in our civilization level. Beyond that point athough less developed we could be accepted for not being harmful anymore.
no.. you're assuming that other species develop technology at a similar rate, and that our current progress will continue at the same rate. Both are things we don't know.
There may be hard limits that stop development of technology past a certain point. Like Moore's law coming to an end, but one day we may not have any viable alternatives.
This is init, with the exceptional property that you write your scripts in Guile Scheme (an implementation of a standardised Lisp dialect). That should allow for a more robust and debuggable way to write init scripts.
GuixSD is kind of immature at the moment, and I have driver issues with linux-libre, but in the coming weeks I'll have the time to try to run it with a custom kernel that supports my hardware. If I succeed, as an Emacs user it'll become turtles all the way for me, which is very exciting (GuixSD is Guix + Shepherd + GNU + Linux Libre).
"kind of immature" is a bit vague, but I disagree. I'm using GuixSD on almost all of my machines (a server, two laptops, an audio workstation) without problems.
It is quite easy to overwrite the kernel package to use in a system configuration (e.g. to use a kernel with the RT patches applied), but I should say that I use the default kernel on all but one machine.
Is this before or after leafing through their book? Because I think there are at least two stages of not-understanding Rust. One is before taking a look at the book and docs in which you can't make any sense of it at all. Another one is after scanning the book and trying some of the examples in which you really start to understand how you can't make any sense of it at all.
Curious, is it harder for c++ programmers to learn Rust than dev from higher level devs? Because ive seen Rust has a lot more success recruiting devs from python, js, even php.
There are two main communities in C++, those that embrace safety and take advantage of the language features to improve their productivity, while going down to lower level constructs if performance needs an extra push.
Then there are those that are kind of exiled C developers using a C++ compiler, forced to migrate to C++ on their work, trying to use it as C with C++ compiler.
That maybe it. Perhaps the first camp is more comfortable and familiar with the "ocaml'ness" of Rust, while for the second (C devs) camp the concepts are alien.
Because the other comment didn't spell it out: effect is correct there. Effect as a verb means something like "to cause to happen". Don't pretend effect/affect is just a noun/verb split. Both words have meanings as both verbs and nouns. It's best to just learn both meanings of each instead of following some rule that's wrong a fair amount of time.
At some point before 31st December (at the latest), according to their blog post. In reality, their website is down right now. Downloads and other sites are up, but the blog is down.
1 Fukushima/30yrs? You remember that places linke Fukushima and chernobyl are contminated for the next couple hundred years, right? Not to mention nuclear fallout, endangered species in those regions, groundwater being poisoned, etc