guys my linux is not booting !
reply:
Find a forest, where no human has ever set foot.
Wait until the full moon rises, and then sacrifice x virgins, where x is the month of the year.
Spill their blood on your device, and wrap in parma ham (if your religion forbids you to make contact with ham, replace it with high quality carpaccio. If you're vegan get youreslf a rope).
Then, build an altar to the gnu God, with feet spelling GPL, and a head that like of a gnu.
When this is done, you shall bow down three times to the altar (thirty if you use tabs), place your wrapped bloody system on the altar, and proceed with dancing on Staying Alive, except you will have adapted the lyrics to your system.
When you are done dancing and chanting, you shall lie down in front of the altar, and you shall not gaze upon your system till daybreak.
Then when the sun rises (sorry if you're in the uk, or one of the poles) you will marvel at your system, thanking the ever potent gnu god forever.

The funniest shit I have ever read 🤣 ... had to share

WASM was a mistake. I just wanted to learn C++ and have fast code on the web. Everyone praised it. No one mentioned that it would double or quadruple my development time. That it would cause me to curse repeatedly at the screen until I wanted to harm myself.

The problem was never C++, which was a respectable if long-winded language. No no no. The problem was the lack of support for 'objects' or 'arrays' as parameters or return types. Anything of any complexity lives on one giant Float32Array which must surely bring a look of disgust from every programmer on this muddy rock. That is, one single array variable that you re-use for EVERYTHING.

Have a color? Throw it on the array. 10 floats in an object? Push it on the array - and split off the two bools via dependency injection (why do I have 3-4 line function parameter lists?!). Have an image with 1,000,000 floats? Drop it in the array. Want to return an array? Provide a malloc ptr into the code and write to it, then read from that location in JS after running the function, modifying the array as a side effect.

My- hahaha, my web worker has two images it's working with, calculations for all the planets, sun and moon in the solar system, and bunch of other calculations I wanted offloaded from the main thread... they all live in ONE GIANT ARRAY. LMFAO.If I want to find an element? I have to know exactly where to look or else, good luck finding it among the millions of numbers on that thing.

And of course, if you work with these, you put them in loops. Then you can have the joys of off-by-one errors that not only result in bad results in the returned array, but inexplicable errors in which code you haven't even touched suddenly has bad values. I've had entire functions suddenly explode with random errors because I accidentally overwrote the wrong section of that float array. Not like, the variable the function was using was wrong. No. WASM acted like the function didn't even exist and it didn't know why. Because, somehow, the function ALSO lived on that Float32Array.

And because you're using WASM to be fast, you're typically trying to overwrite things that do O(N) operations or more. NO ONE is going to use this return a + b. One off functions just aren't worth programming in WASM. Worst of all, debugging this is often a matter of writing print and console.log statements everywhere, to try and 'eat' the whole array at once to find out what portion got corrupted or is broke. Or comment out your code line by line to see what in forsaken 9 circles of coding hell caused your problem. It's like debugging blind in a strange and overgrown forest of code that you don't even recognize because most of it is there to satisfy the needs of WASM.

And because it takes so long to debug, it takes a massively long time to create things, and by the time you're done, the dependent package you're building for has 'moved on' and find you suddenly need to update a bunch of crap when you're not even finished. All of this, purely because of a horribly designed technology.

And do they have sympathy for you for forcing you to update all this stuff? No. They don't owe you sympathy, and god forbid they give you any. You are a developer and so it is your duty to suffer - for some kind of karma.

I wanted to love WASM, but screw that thing, it's horrible errors and most of all, the WASM heap32.

People having sleep deprivation.

If your health is at stake, you may want to aim for maximum healing potential.
Humen always should prefer more natural substances and techniques.
As chemicals mostly alter the status quo but tackle the ultimate reason why.

Military has developed glasses that simulate the sunrise to wake you up / keep you awake.
That technique is like 20 years old. And who is gonna get those glasses for me?
Nowadays, studies published find humen feel more at ease by rising and sleeping with the sun and moon.
Having two weeks of camping once in a while is recommended. At least once a year.

Alternately you can try to regulate your days rhythm.
Start your day with a cup of hot speedwell tea.
Like every freaking day.
Its augmenting your activity thus easing your sleep at night.

Give every technique at least two weeks time to take effect.
And always remember :
Sleep is a thing that can be influenced but never will be controlled.

Good night ;P

when you have coded the sun the moon and the stars. but the motherfucker still wants a universe engraved on a fucking ice cube. AND YOU'LL DO IT ANYWAY. CAUSE YOUR HIS FUCKING BITCH. YOU GUCKING GUCK!

Sorry fam... Just because I was a devOps in my last job doesn't mean you will get the sun and the moon when asked. Let's talk realistic solutions with resources.