bmarkovic

In JSON the de facto standard for datetime is (because of JavaScript) very much the Unix msec timestamp (which is always in UTC) so while it's not hardcoded in spec you basically need to be an idiot not to do it like that, and removes one huge headache of XML dates which is timezones.

Few years back, Convey[1] has apparently outran HAProxy in an alleged benchmark by the author[2]. That's a one man project (now abandoned, sadly) outrunning a decade old product built by an enterprise company AND a big community AND spearheaded and designed by a data structure genius. Granted, only in one of many tricks HAProxy can pull, but still. Not a database but indeed a concurrent world-facing RealWork software. If true (didn't actually check myself), I'd say it fits your bill.

Personally, I read that as "can be as fast as, but without you having to be Willy Tarreau level genius" which is all I need.

It's easier/more-intuitive to do a lot of things in C++, but safe, high performing C++ is certainly harder than safe, high performing Rust for huge swaths of use-cases. Also, as has been mentioned, its type system that benefitted from the PL research since the 80s also allows for nicer expression of business logic. In particular, this means that in Rust, unlike C, Go, or even C++ in great part, you are not writing in the same low-level intricate language at every level of your stack i.e. it can be a nicer high-level experience the higher you go if you designed your lower tiers well.

And that last thing to me is the biggest advantage it has over the competition.

Off course, there is also the fact that juggling dependencies in a non-trivial C++ project was a nightmare until recently with vcpkg and it's manifest mode and that will take probably another decade to become commonplace in the ecosystem (if ever).

[1]: https://github.com/bparli/convey [2]: https://bparli.medium.com/adventures-in-rust-and-load-balanc...

All nice and dandy, but a coroutine, and doubly so a goroutine, is still a coloured function.

HackerNews is really a bubble sometimes. I don't get who the "many people" that "got used to macOS" are.

Apple had fiery fest of sales in Q4 2021, outsold all Wintel manufacturers, let alone Chromebooks. And after that, guess what, they now have 8% of desktop/laptop market share, instead of 6% they used to have. You can guess who covers most of the other 90+ percent.

Sent from my 2021 M1 Max MBP.

So XFCe == GNOME and LXDE is GNOME or KDE, depending on which version we're talking about?

UI toolkit doesn't equal a desktop environment. There is tons of stuff in the GNOME ecosystem (some of which it will make a lot of sense for System76 to reuse, no doubt) that can be entirely ignored when you're using GTK to, essentially, draw your UI widgets for you.

I am perfectly content with how things are now.

I still collect things I care about, I have tons of FLACs (some ripped from my CDs, some bought online) from artists that are meaningful to me and whose music is significant in my view.

I'm still grateful for Youtube and Deezer (I hate Spotify's UX so I'm never there) for providing me access to music I wouldn't necessarily collect, but I'm now also not at will of some radio DJ when I want that kind of ephemeral music in my life.

Open Cycling Maps combines OSM data with open source topo data and works really well. The gold standard for digital hiker is a gpx track made by experienced mountaineer, on top of OCM.

Between that, satellite imagery and offline capabilities of a modern phone and a hiking app that supports these formats you're all set.

The reason that you should have a topo map and compass, and know how to use them is that your battery cannot be expected to serve you throughout a multi-day hiking/camping trip.

What a way to avoid dealing with actual arguments.

Btw we don't.

Most law breaking in entrepreneurship is usually finable misdemeanours. Like 99.99% of it. We don't call those people criminals.

They're probably a native speaker of gramatically gendered language (like German, most Slavic languages etc).

It is also a frustrating experience to endure reloads on every click if what the user is using feels like a web application and you're essentially placing that burden of reducing the interaction roundtrip time on your infrastructure which gets expensive really really fast.

Most web-thingies are neither 100% plain websites nor 100% plain webapps, most are in the middle, some are heavily leaning on one side or the other.

I've only used Vue SSR / Nuxt this way, so there might be a fundamental difference in the implementation, but hydration process in it isn't blocking, and whether or not it's slow greatly depends on how heavy your webapp is.

The page that he browser is hit with has ALL the content pre-rendered (sans CSS) in that first HTTP HTML response, and it behaves like a classical webpage henceforth until the moment that the interactivity bits are being hydrated which is deferred.

I concur that it's still a bad idea to use SSR SPAs for use-cases where a non-dynamic HTML page would work decently well, and there are ways to pack some of these frameworks (Vue in particular) so that it's a JS dependency of an otherwise functional webste (i.e. progressive degradation) for a lot of the in-between use-cases, but when what you're building is heavily leaning towards being essentially a web application (say, an e-commerce site, webmail client etc) then SSR is certainly the most viable option for a decent user experience that isn't full reloads on every click, but also doesn't take ages to become interactive.

WIPO / Berne rules are guidelines. Not even in the Western Europe which aims for "feature parity" with US copyright laws are things the same (case in point: treatment of copyright and patent ownership of things invented while employed, yet not at work or in relation to work).

So they simply do not apply even broadly to a case that was processed in China, especially not in the level of deep US-centric scrutiny you applied to it.

That said, I don't see any of the "multiple test" this ruling fails. It has simply posited that verbatim copying of the article published on one website to another website without prior agreement is still copyright infringement, regardless of the fact that the article itself was generated by software/AI. Nothing more, nothing less.

I find it hard to imagine that a court in any other country would rule any differently.

The fact that this industry turned to a proprietary low-quality solution like Slack when Riot/Matrix have already existed tells the full story about what a bunch of incompetent idiots we all are.

Everyone frustrated with the new Slack input box deserves what they got. Me included.

People growing up in western society have become so egocentric it's absurd. We've finally made it, we're incompatible with what human society has been for thousands of years and to some extent still is in Asia -- "discipline" has finaly become the biggest cuss-word and the most horrible thing ever.

Sure, the world doesn't need more people, you certainly don't NEED kids but come on.

The key reasons boil down to "you'll have more responsibilities, it's hard work, and will need to share your life with other people and not make it all about you". You even somehow managed to utter "the company you founded" in that same sentence.

Having done both, I'd say raising children is actually lot like starting a company, just requires a lot more discipline and is more stressful. It would happen that I tried to do both at the same time, and both are hard work, you pile on responsibilities, reduce hobbies and "me time" and become responsible for other people's lives in the process and in both you're essentially fucked without strong willpower and discipline. I wasn't good enough to do both at the same time so I sold off and left the company and got a well paying 9-5.

Btw the ticket out of the "children situation" for man-children (and sorry but you managed to paint yourself as one) also exists, it's not impossibly hard and, assuming you'd do your fair share of obligations, could possibly even benefit your wife and kid(s).

I too hated the lack of "me time", don't get me wrong. I had a hobby I was deeply passionate about and really got back to it (and still fairly infrequently) only when my kids were well into school age. I also gained about 12 kg (some 25 pounds) that it took me years of gym, running and mountaineering more-less just to halve and I don't really go down from there (tho my "build quality" did improve :) ). I've also halved my learning rate in things, had to rearrange my priorities and generally "streamline" my career in many ways.

But here's the other side of it. Had I not become a parent I'd probably have fucked up my business. Neither of the issues were me not having enough time -- most were not knowing enough, not being man enough and not being mature enough. The children might have hindered my speed of improving in the first thing but have made me surmount a Mont Everest in the latter two -- which I don't feel that I would be able to (short of some traumatic experience). I'm much more confident as a man than I would ever be without having them and knowing them.

Also children return on that investment of time, nerves and forgoing with (at least in that age between two/three and puberty) unreserved love you'll never witness (and I've had dogs and kitties so, no, sorry, no contest there really), and later, with slowly becoming men (well, people, It's just that I have two boys) and although much of their accomplishment has fuckall to do with you, you can't help but be filled with pride.

I regret a thing or two in my life, but having them was the best damn thing that ever happened to me.

Good luck doing code reviews with a distributed team using that.

There are valid reasons for a "never rewrite history" policy, but their validity pales further you go from the master branch.

The thing is that in a lot of scenarios people need to do huge chunks of work in feature branches. Sometimes a 3000 line "refactor the world" squashed commit is really unhelpful. The best policy is always well thought of weighted case-by-case decisions.

However, on projects with a lot of hands on the keyboard such policy is unrealistic and someone will do the opposite of what they should and wont ask or discuss. People, especially in our business, hide incompetence behind aloofness and silence.

So in that case, with a lot of people that are hard to manage, stiff policy is the best choice and there probably are reasons why people want to preserve history, no matter how hairy it looks, at least it's there and you can find stuff in it.

And then leadership hires good lawyers that do their best to deflect the blame to the developer.

As someone who had to deal with them from both sides, EU public procurement laws are fucked up beyond repair. There is, however, a simple cure for software that the public sector is avoiding in most places:

1. base the software on an established, battle-tested open source product, there is one for almost any business case

2. use the money to hire an in-house team, hiring norms in public sector at least ALLOW for quality selection, unlike public procurement ones

3. develop in the open, invest into visibility, attract community members

4. shill, try to get as many agencies across your and other member states to pick the same solution and co-develop the software with you, this way the cost drops for everyone

Even if you can't find something to satisfy point 1., the other three points would still work to your benefit. If you can push this for long enough to make the software standard in more places, you could get a critical mass of outside developers to form consultancies you could hire later for additional work.

I know Munich is poster-boy of this not working for desktop OS-es but that's really a consequence of two things:

1. They made all the wrong choices (heavy customization, chasing windows look and feel, not tracking upstream progress)

2. They got elected officials who were effectively Microsoft shills (the top-down decision to go back to Windows was heavily pushed by a single executive who was pissed off he couldn't use Outlook he was used to on his previous drone job).

Perhaps. But those that they spy on (spouses, children, employees..) don't.

Biodiversity will recover on a planetary timescale. Our civilization will probably be lost tho.

Given how most polution comes from places where people generally have very little children, I doubt that reducing births in the third world would be an effective measure.

We need to solve for different variables: energy source (we need more nuclear), transportation (we need people to utilize public transportation and drive less cars), and we'd need to work on carbon capture (which is a technological problem).

Solving all these requires policy shift and government enforcement.

So you're arguing that the third world doesn't deserve washing machines and clean water, so that you can have one person per SUV in the states?

Except that EU has been doing it's job since the 90s and China has been doing it as well in recent years. They both slipped the last 12 months and a lot of it, at least in Europe is combination of side-effects of the post-Fukushima nuclear scare and increase in greeny renewables (like solar and wind) that actually cause more methane and coal to burn because they cannot work as reliable base supply.

You are right about anti-GMO but my experience with antivaxers was that they were predominantly anti-science, often highly religious and more commonly conservative or fringe right than the other way around.

I don't think antivaxers are predominantly left wing. The whole Big Xxx (in this case Pharma) paranoia has long since left the camp of rational scepticism over suspiciously funded research and into the realm of uneducated lunacy that plagues both fringe ends of the ideological spectrum. But it is definitely more right aligned because it resonates well with the whole "my beliefs are at least as good as your scientific facts" thing that is firmly a right wing thing. This is further compound by the facts that fringe right is extremely well correlated with lack of education and by some studies even with lower IQ.

If ($)emit is not something you use for very ephemeral events, that otherwise cannot be expressed as state changes in natural way, or in a custom, reusable component (i.e something you could publish separately from your application), you're using it wrong. I rarely ever use emit and when I do it's either a very active reusable component or a solution for an otherwise very difficult problem. And I don't see what a meaningfully prettier/better API would be.

Except that, unlike realworld, this is about as useless (for proper comparison) as the OP app if not more.

JSX is PHP-mix-HTML templates and JSP all over again. Those that fail to learn from history are doomed to relive it.

Recursion IS hard to reason about, and then implementing it efficiently (in a runtime / compiler) is also hard, and then an efficient implementation restricts your expressiveness, and then when someone else needs to read such code, it's hard for them to reason about it.

There are actually a lot of similarities with React.

Neither are useless nor bad per se, but given options, in majority of cases both are more of a smartass thing to do rather than the most optimal or most maintainable / developer friendly thing to do.

I'm pretty sure that, while they apparently party much harder on their private time, north-western Europeans appear to be much more "prude" in their work life than any other group in the world.

I also believe it's actually a part of their cultural inclusivity. It's a very stressful pressure if you're expected to go to a strip club with your colleagues after work if you're female, gay or in a relationship where such behavior would be sanctioned by the other party.

Americans and Asians apparently expect others to "fall in line" in all corporate policy matters, including this one. So as a result of globalization the corporate policy matters that one is expected to "fall in line" to have slowly become the least common denominator of all this cultures and that's the type of business chastity that is normal in today's HR rule books and everything outside is hastily sanctioned.