ldng

46 ms·

541.
by ldng 8y ago
Well, I hope they don't. Functional extremism killed Scala for the wider public (IMHO)
542.
by ldng 8y ago
Make it fail. I'm going to flag as SPAM any mail that comes with AMP in it.
543.
by ldng 8y ago
As far as I understand, it is using GTK+3 but following the GNOME 2.0 Human Interface Guide.
544.
by ldng 8y ago
Well they are not. Yet. It is a deprecation notice and at some point they will break userspace. You're quote is a matter of context. When Linus say never break userspace, I understand it as : never break userspace without warning and c
545.
by ldng 8y ago
Maybe you missed the disclaimer ? "The code below is intended to be simple and educational, NOT optimal."
546.
by ldng 8y ago
Nor did that changed anything. Most employees are contractors nowadays. French politics must stop playing with trains and grow up. And fire the management that's been there for 10 years and made it worst.
547.
by ldng 8y ago
Now combine that with Apache Arrow and you can do some interesting things.
548.
by ldng 8y ago
Hum, right, parts of TLS could be offloaded. Now will the TLS protocol will continue to evolve ? And will QUIC follow ? And you could offload UDP, TLS but not QUIC itself. Unless you're BigBuck Company and offload to FPGAs competition
549.
by ldng 8y ago
It is probably too late, for later reference, when this talk is up, check it out, it has some answers. https://fosdem.org/2019/schedule/event/breaking_postgresql_o...
550.
by ldng 8y ago
One thing I don't understand is, if it's encrypted, we'll never see hardware accelerated QUIC ? I've read it's 2 to 3 times more CPU intensive, aren't we implicitly giving an artificial competitive advantage to
551.
by ldng 8y ago
It's to improve Google Car
552.
by ldng 8y ago
I think you missed the shift. It's all about internet openess now. Not sure the end user is still in the equation.
553.
by ldng 8y ago
There was Rancher 1.6 with Cattle was the sweet spot for us. Rancher 2 went full kubernetes. Probably makes sense for their customers. We're looking for a replacement in that sweet spot.
554.
by ldng 8y ago
Well next fine, if nothing is done to comply, will be heavier. For better or worse, that's how it is intended to work.
555.
by ldng 8y ago
It is addressed in the previous article of the serie.
556.
by ldng 8y ago
That is called a standard. You want it to settle down.
557.
by ldng 8y ago
TCP is not only used for HTTP
558.
by ldng 8y ago
And vs SCTP. A deep dive impartial comparison at different usecase/workload would be great.
559.
by ldng 8y ago
In HTTPS, nobody. Else, proxies ?
560.
by ldng 8y ago
> But alas it's too late. QUIC has been in development for six years now. So what ? We standardize on a hack because Deep Pocket ? Not even mentioning competitive advantage for big cloud companies ...
561.
by ldng 8y ago
It needs industry's adoption. It's probably the better long term solution. But why bother when you can hack a wrapper around UDP and pretend you're long term planning for the "greater good" ?
562.
by ldng 8y ago
Fascinating. I wonder if the reverse could be found. That is areas where educated "elites" were decimated and education level plummeted.
563.
by ldng 8y ago
> I usually take the time to write long explanations as to why these points are invalid Could you link to one of your long explanations ? I'm interested in a rebutal but understand it's annoying to repeat yourself.
564.
by ldng 8y ago
It's not one standard. It's about having a huge head on the on all the important internet standards and pushing their cloud interests. It designed to work well at their scale on their network you connect to directly. The standard
565.
by ldng 8y ago
Which Google can afford. Oh look your small independent cloud provider is slow, come to Google Cloud. They've been subverting standards to push up the cost of entry and very few people have calling them out ...
566.
by ldng 8y ago
IANAL, nut I would say 2. You can alter a contract proposition. It was up to IBM to check what was actually signed.
567.
by ldng 8y ago
Oh dear and me wrongfully thinking there was a huge amount of money at stake!
568.
by ldng 8y ago
> you need to motivate your decision & respect the process. And still you can fire someone. And now, with recent reforms, you know exactly how much it will cost since it is a fixed grid.
569.
by ldng 8y ago
Hum, no it was not her. I think it was a Google I/O on googlevideo at the time but I could be wrong. My memory is a bit fuzzy.
570.
by ldng 8y ago
Not the best I've seen but definitively one I would like to recover the link to : a Googler presentation where she explain how they took about 2 years developing a memory optimisation (circa 2007~2009 IIRC) and manage to finish a few m

More ›