And 3d renders look like read world photos. Can't trust anything anymore \o/
683 karma · joined January 29, 2016
jylam at lnxscene org
> "Is my timing bad?"
No it's not. There never had been such a demand for developers, don't let yourself convince of the contrary because of some thousands of FAANG's layoffs. Thousands is nothing on the market.
Aren't homing pigeons getting back to their "home" ? So the pigeon must have been raised in the prison, right ?
You are welcome.
To add to everything you said, the Covid crisis also impacted maintenance, delaying repairs by about a year (source: I've got surprisingly many friends/colleagues coming from the CEA, the French Atomic Commission)
Also, EDF lost a lot of knowledge and manpower during past decades, (most? at least many of) people working on nuclear plants are now sub-contractors, that impacted stability.
People are not a bunch of idiots. Climate change is very real. Using other sources of energy requires investments. It is mandatory. All those are facts, as far as I know.
If your only arguments are "it will hurt the economy" and "people won't understand", you didn't take the measure of the problem and are part of it. That's very short-sighted, and tends to prove you don't really know what you are talking about.
But in this case it does, what's your point ?
Like "entrepreneurs" (whatever the author makes as a definition) are fundamentally not "regular people" (whatever the author etc.). What kings can learn from peons ? Everything, kings know nothing and rely on other people to do everything. They only have the means (the money) to motivate them.
Shit we all lost 5mn.
I'd hate to see that happen, and I write C every day, read hundreds of lines of C everyday, and actually formally prove C everyday. C is not meant to be Rust or Go or Java. I'm actually against most of additions those days to the new standard. They complicate things, the (barely) portable assembly it's meant to be. I wouldn't write a database in C today, but I'd be happy to start a new bootloader project in C tomorrow.
The author is actually angry that the OSes still expose a C interface when they should use something higher level, like it seems Apple is doing (I may be wrong). I get that, but like we say in France, don't discard the baby with the bath water. The problem is that, as they say clearly, C is the lingua franca. C isn't the problem, its use is.
To me, it seems quite evident, they need to reduce the spending for any reason, so they reduce the workforce. Nothing to do with useless employees. You can be shit at your job or very good, they will have a metric threshold telling them you need to go. Same at Twitter, Meta, Google, whatever.
Stop putting that on the employee who spent 3 months to get a job just to be told they wasn't useful. That's 'bad' managing all the way down, nothing to do with the employee, at all.
The "faute grave" you are referring to is the "faute lourde", for which the employee voluntarily caused harm to the company. A "faute grave" is more like a big mistake, harassment, misbehavior, etc.
Basically, you can fire anyone you want if you pay for it. But you'll have to pay, and if the employee is not happy with what they receive, they can go to court (which is very long, most of them won't).
Finding a job is easy for us those times, you don't risk much. Finding good workers is hard for them, the balance of power is on our side.
I tried Rust, wrote a raytracer and a GameBoy emulator to learn the language. But I still find it VERY hard and slow to write on a daily basis. You can't just test anything with it. Either you thought the whole project well at the beginning, or you'll need to rewrite everything from the start.
I understand Rust is meant to be clean, no undefined behaviours, everything explict. But as a C programmer, that's just the opposite of what I am accustomed to.
Are there documentations, books, tutorials, whatever, that explain to someone like me how Rust works from a C expert's perspective ?
(To be clear, my brain is NOT a clean slate, and I think we are legion. I've spend sometimes days to understand how to clear a Rust compiler error, and it ends with the copy of a whole megabyte of a structure because I don't think how I should think in Rust)
Of course you won't write anything that you hate at first, because it's for fun. But hating something for some days or weeks is part of the fun, too. You are challenging yourself, not doing it the easy way, to appreciate how well the others are doing.
If you want to turn it into a business, so yeah, don't write a graph visualization engine, or crypto stuff, or anything really. Get a job, that can be fun too, and let the entrepreneurs figure out the rest.
the C Standard has a thing called "undefined behavior", and this person is running right into it with their invalid pointer arithmetic. So the result is undefined, and could be anything, including embedding the Doom source code.
105 miles is 168km, they say 20mn end to end, that's 140m/s, or ~500km/h. So only from one end to the other, no stop. Even by electrical means, that's very loud, try to stand near an high speed train in France or Japan. In a tunnel ? Good luck if there is the slightest problem with it, you are stuck. Goods, food, whatever ? Tough luck, you have nothing to eat for days, weeks, months.
That's obviously a place where the government does as it pleases, you won't be rioting there. 100 cops and you are stuck. You are probably living far from the top, no solar power, no water, no food. You bought yourself total dependencies to someone. A king of some sort.
No cars or roads, you only depend on the state for moving more than 6km/h in the best case scenario, but there are 9 millions people trying to move as well.
Who the hell would want that ?
Those CPU are very simple, you have like a dozen instructions, 4 or 5 addressing modes, that's it. You can infer the cycles count from each instruction by the addressing mode, mostly.
The machines those CPU run are a bit more complex than just the CPU, but after some time you get to know them perfectly. You can think about an algorithm in your shower or on the way back from work, and code it like a robot, directly from your brain, you figured everything out to the last detail just in your head.
That's very, very rewarding. I've never got this kind of feeling while playing those coding games, like Zachtronics's, although I've enjoyed some of them. I played Factorio for hundred of hours, that's very pleasant, but the UI gets in the way and you know the problem already has been solved.
I very much encourage you to try assembly on 8bits computers, coding graphical effects and demomaking stuff and all. That is, if you don't have kids and all, that takes time :)