kunley

27 ms·

391.
by kunley 3y ago
Very interesting to read as a former employee of a company being Gitlab's customer, self-hosting EE production and solving everyday problems, with their support also, during the described years
392.
by kunley 3y ago
RDS is not so bulletproof as advertised, and the support is first arrogant then (maybe) helpful. People pay for RDS because they want to believe in a fairy tale that it will keep potential problems away and that it worked well for other cus
393.
by kunley 3y ago
A fallacy of a "choice" between GCP and AWS never stops to entertain me
394.
by kunley 3y ago
And that article is filled with junk ads every paragraph
395.
by kunley 3y ago
This book is a pearl, esp. the second part with a VM-based interpreter. Not sure why the OP posted this particular chapter, maybe because IIRC there starts a sketch of Pratt parser implementation
396.
by kunley 3y ago
It is so funny to defend serverless with it's all crappy configuration, slow dev cycle and vendor lock-in.
397.
by kunley 3y ago
Fortunately in Europe what the said boss did is illegal and this can end with a criminal prosecution.
398.
by kunley 3y ago
Interesting that only with an advent of IoT it became obvious, that it is hard or impossible to upgrade some systems and that writing software for small devices can be very cool. (Having said that, I detest the usage of win3.11 here anyway
399.
by kunley 3y ago
These letters seem fake. What is the real reason behind this site?
400.
by kunley 3y ago
At one job, Canonical was our vendor and I need to admit, they tended to be arrogant also towards the paying customer.
401.
by kunley 3y ago
The evaluations don't magically/implicitly happen on many cores. I guess the first thing worth doing when analyzing this would be looking at the differences in the bytecode, then looking at the C code implementing the differing by
402.
by kunley 3y ago
I would guess it's the corruption of tenders in the public sector. The organisation in the public sector must choose the right vendor and then any sh*t sold by this vendor is correct, otherwise it would prove the wrong choice.
403.
by kunley 3y ago
Funny how some people in the comments here are calling the OP's hardware as inferior in terms of computing power, while in reality their software is often being run on production on much more limited resources paid with quite a load of
404.
by kunley 3y ago
Nice recap. By the way, just curious what is your opinion on MessagePack?
405.
by kunley 3y ago
I start to believe in this case "unorthodox" means "stoned" or something
406.
by kunley 3y ago
You do actually realize that on the home page you're having something like a restaurant menu, do you?
407.
by kunley 3y ago
The author goes deep in explaining not only the technical details, but also the motivation why things were crafted in a certain way. Actually all of his articles on Ruby are like that, personally I like it a lot
408.
by kunley 3y ago
This talk is great in its revealing of history, does it in a very meaningful way. I had few romances with OCaml over the last two decades but never had a broad view on the different phases of its evolution. Anil provides a lot of insights a
409.
by kunley 3y ago
I think they fired him because they are _not_ close to the AGI (no one is), but he lied to the potential investors how they are. That's against a popular sentiment about the upcoming "breakthrough", but also most probable giv
410.
by kunley 3y ago
It is not about vendoring. Vendored dynamic libs would be depending or other libs or even on glibc that does not exist anymore. You can't recreate the dynamic libs environment. With static you don't need that environment, only the
411.
by kunley 3y ago
It's very far from true for many of languages. Tried to gradually upgrade projects written Ruby and Python, that were not touched in 10 years. The dependencies were based on C extensions that depended on libs not existing anymore. It w
412.
by kunley 3y ago
Naah, in my observation it is kind of bashing which is almost always around the fact that Go is not Rust, which amazes me each time why certain individuals do that instead of simply coding in Rust or writing more about Rust. (Funny that it
413.
by kunley 3y ago
Someone could also write a much more bitter article "N Years of Go Hate", as Go bashing became a very popular trend, also unfortunately here. In my estimates N = 6, more less
414.
by kunley 3y ago
Wow. Sounds almost too surreal to be true. Is it really that demoralized in the management there? That's scary.
415.
by kunley 3y ago
"Antiethical". Is it true that mindless bashing Go became some kind of a new religion in some circles?
416.
by kunley 3y ago
I'd talk about a common sense definition of a mistake, but common sense is so undervalued nowadays, that I don't even know how to start conversation about it. By the way, can you give a concrete example of a team mistake being org
417.
by kunley 3y ago
"it requires no configuration or setup", still every single example comes with a config file. WTF? If you look at it more closely, it can be seen that there is no configuration needed for pattern discovery, but there is for colors
418.
by kunley 3y ago
"It is really, really hard to organize a large group of people towards any common purpose" Well, one very healthy rule to organize people is that people are responsible for their mistakes, which has a long-term effect of having le
419.
by kunley 3y ago
Here is a story not about wasting cloud resources, but about wasting careers: A decade-long project at the ThreeLetterYouknowwho was turning into a separate business, so people were being convinced to abandon their dozen-years old employmen
420.
by kunley 3y ago
Can you explain?

More ›