JustLurking2022

Because it implies these are people have far fewer excuses for the seeming lack of care about user feedback than some unpaid volunteer.

Considering many companies have contacts ranging from millions to hundreds of millions with Microsoft, and developer tools are a major selling point for the ecosystem, it's certainly reasonable to be upset that when your organization can't depend on them. It makes planning a nightmare - it may take a month or 5 years to deliver your feature, depending on when the bugs get fixed.

And statistically, they're virtually all correct.

This seems like it should be identified as an Ad, rather than an organic post.

Thousands of simultaneous sessions isn't all that many, if you are scaling your infra to dozens of servers. Can be handled by a single server, if code is optimized.

My solution is aggressively unfollowing or disconnecting from people. There may still be a lot of low value interactions, but at least I don't have to see them.

Very often find an answer

- from 10 years ago, and an entirely different version of the language/library

- from more recently, but it's been closed as a duplicate

- with a specific caveat, but that guy ignored and the question was also closed as a duplicate.

- with a wrong answer, that you'd like to post a correct answer for, but you haven't karma farmed enough

I've been using ASP.NET MVC since the preview and wouldn't touch this. It actually feels more like the old ASPX web forms where the components were inscrutable black boxes. Ultimately, I think it's actually better to have separation between UI, client-side state persistence and server-side frameworks.

Getting these kinds of applications out of Silverlight or desktop apps was one of the greatest steps forward I've seen in at least a couple large enterprise shops - and Blazor definitely feels like a step back in that regard.

Honestly, it's one of the issues I see with WASM as a whole. The JavaScript ecosystem is almost implicitly supportive of open source, since that's essentially what gets delivered to the browser. WASM feels like it take us back towards walled gardens where you have to buy Telerik or Dundas libraries to get the widget you want to use, and then find out they don't play nicely with some other part of your stack. For all but the must graphically intensive use cases, or companies that can afford to own their stack from the ground up, I see little reason to adopt it.

The distance computation could be separate from the indexing, but it will be inefficient relative to having an index organized to support the task.

I'll bet the publicize whatever benchmark looks most competitive to get the next funding. That's no criticism, just the way every business somewhat has to work in a competitive industry.

Technically there's also a path where people become less racist so ethnicities matter less.

I think that's an area where the average person in the U.S. struggles. For all our issues with race, we are generally fairly integrated, so the thought that national borders need to very closely reflect ethnicities isn't top of mind.

Holy hell does that sound awful. In practice, it doesn't even solve the core problem as you'd have to deploy new versions of all binaries precisely in sync to avoid data incorrect because some clients know about the v2 table and others don't. It becomes indistinguishable whether a row is missing because it was intentionally deleted or because it was written by a client who didn't know any the new table version. There are ways to account for this but it's layers of crap on top of crap.

Seriously, is there an email distro or something to notify Nix users when there's a new post to go troll? It's not suitable for 90%+ of users, which seems a far cry from superior.

Other than saying "ad targeting bad", not much to go on here - the article makes no reference to the specific laws plaintiffs believe Google is violating

Not that it happened but the fact that you consider up to 10% population loss acceptable is truly astounding.

Think about this one for a minute - if companies paid for this type of stuff, they would expect to have a say on exactly where you live. Not "you need to be within driving distance of the office" but more like "you need to rent next door to the office". Yes, there are very good reasons the cost of commuting is left in employee hands to decide.

If one of you is from one corner of the former British empire and the other from another corner, it becomes a lot less surprising. The British showed out everywhere the past ~400 years and often forcibly relocated certain subjects (e.g. the Irish).

I think the real question is around the distribution of performance of the people who leave as a result of RTO. If it skews towards the higher performing end, then it would greatly call into question the assertion that RTO will make the company more productive.

This article reminds me how FAANGs are great at coming up with all sorts of extra roles/job responsibilities simply so someone can pay themselves on the back in their end-of-year and/or promo write-ups.

It also feels filled with "assume a perfectly spherical cow of uniform density" oversimplification. While the roles are certainly different, so are people, teams and companies. Very often, optimizing for those strengths/weaknesses is more important than some universal rule about the appropriate breakdown of responsibilities between roles.

While it's definitely interesting, I do wonder to what extent WASM threatens the open web even more than the DRM battles of the past, perhaps in non-obvious ways. I'm the past, one of the ways many a frontend dev has picked up tricks was simply by reading the JavaScript for a site they liked. That can be made harder by obfuscation but, even then, a prettyfier can make things generally intelligible.

That exchange of knowledge was possible because a) for all it's warts, JavaScript became the standard for everyone in the field and b) the only way to publish your work was to publish the source (at least a derivative). WASM blows away both of those assumptions and takes us in a direction more similar to desktop software, where you may have a copy of the binary but may not even (easily) determine which language it was written in.

We don't know how aware they were of they initial fraud - maybe not at all, maybe more than we've heard so far.

That said, we do know that he committed several additional offences, including the ones described in this article, while under house arrest at their residence. That alone should warrant further investigation and call their conduct into question, along with their standing in the legal community.

It absolutely would if you remove the cut HFTs take out of the market. I'm sure you'll make some argument about liquidity and spreads but, in the aggregate, the money from higher spreads goes to market participants so the market as a whole still saves by eliminating HFTs, even if the spreads go up a bit.

Worked in an investment bank, although not in a client facing role, and it's not quite as simple as it seems - if your client reaches out with a question via text or WhatsApp, technically you should redirect them to use your bank's secure messaging app of choice.

The problem is no one has ever heard of Symphony, doesn't want to install it so they can ask a simple question, and the user experience is meh at best. If you do the right thing, clients would likely perceive you as difficult to work with and perhaps go elsewhere. To done extent, the inevitable fines might be seen as a necessary cost of doing business. So a pretty severe crackdown was necessary to ensure everyone is properly incentivized to inflict this pain upon clients.

It's good for someone on each side, but necessarily the population at large on each side...

Plenty of dictators will happily sell off their country's natural resources to line their own pockets, and the same general principal holds true for many other types of transactions.

You could easily solve all of this without HFTs - you might introduce a few seconds of latency but virtually no real investors care about that level of latency and it would save them billions per year.

Humans can just as easily read an OpenApi spec.

Based on the large discrepancy with levels.fyi, I'm betting that person either put down their total comp as salary, or they are a very specialized researcher in an extremely hot area (probably AI).

He had to go through a lawsuit to get them... kinda like the story.

Hilarious you claim something isn't based on any real evidence, while providing zero evidence to back the claim up.

What an absolute pile of nonsense. People who author creative works deserve to have control of them and make some money - otherwise you'll soon find we have far fewer great authors, artists, etc.

This is essentially the same as saying builders charging for houses is the problem with the housing market, so we're going to phase out paying builders.