davidron

So true.

I think you missed flash. And arguably, to the author's point, JavaScript in browser (not wasm).

Totally. Remember slashdot in the 1990s used to house a dynamic page on a handful of servers with horsepower dwarfed by a Nintendo Switch that had a user base capable of bringing major properties down.

I work at a 20-year-old mid-sized SaaS company. As long as the company has been around, product managers have longed for more engineers and strategies for engineers to ship features faster. As of around February, those same product managers across the org are complaining that they can't keep up with the pace at which engineers are shipping their features. This isn't just lines of code. This is the entire company trying to figure out how to help the PMs because engineers suddenly stopped being the bottleneck.

I don't know about 10x, but this could only happen if PMs suddenly got really lazy or the engineers actually got at least 1.5x faster. My gut says it's way more because we're now also consistently up to date on our dependencies and completing massive refactors we were putting off for years.

There are lots of reasons this could be the case. Quality suddenly changed, the nature of the work changed, engineers leveled up... But for this to have happened consistently across a bunch of engineering teams is quite the coincidence if not this one thing we are all talking about.

It's perfectly legal to train a human on copyrighted work and I think, depending on the country, it's not settled that training ai on the same data is illegal.

American here. My experience is that the US dollar seems to be accepted in tons of stores in countries all over in the Americas Europe and Asia. Trade is trade it seems.

As a regular human who plays games and doesn't know about chip architectures, one woud probably lump the wii and the switch closer together than the game cube based on the modes in which one can interact with the systems.

Wii is a game cube with a funny controller. Or, wii is a tv-only olde switch.

I appreciate that it has its own name due to being a transitional experience.

The bottleneck of most applications is acquiring enough users to hit a technical bottleneck.

Or non native English speaker who pronounces "may" the same as "might" and didn't realize the difference?

It is maybe not coincidental that "may" and "might" mean nearly the same thing which bolsters the case for auto correct gone awry.

For those that haven't read the article yet, scroll down to the flame graph and start reading unit it starts talking about back porting the fix. Then stop.

Isn't there a carve out in copyright law for fair use related to educational use?

I bet Microsoft would do something similar. If Microsoft entered an agreement with another company, Apple for instance, to build a version of word for the Mac, a fork, and part of the license has a requirement to attribute in the help file or something like branding requirements, and then Apple doesn't do it right, then Microsoft reaches out to Apple and tells them to fix it else be in breach of the license. They fix it, happy happy. They don't fix it and lawyers get paid.

This was MIT licensed open source software and an attribution clause was not properly respected. Hardly piracy.

Handspring Trio had a web browser by (before?) 2003 with a touchscreen. I loved mine!

This is EXACTLY what I remember people saying about Cell Phones and PDAs when they were popular in the 90s (people can't remember phone numbers any more), Google when it was first unleashed (people won't know how to use card catalogs and libraries any more), and then again about Wikipedia when it became popular. What actually happened was that behavior changed and people became more efficient with these better tools.

The name and address is valuable because it can be matched to offline behavior through a bill you pay or rewards membership you are enrolled in to further enrich the data associated with id_8z6748dxzh and combine it with your shopping history at Macy's and Safeway, for instance. This is even more valuable when combined with your cellular bill.

I've work in ad tech,and with CDPs for nearly 20 years.

... If incentives were properly aligned to make this the correct strategy, then this is probably what McDonald's would do. Unfortunately not. https://www.today.com/food/trends/why-is-mcdonalds-ice-cream...

Education is a patch. It's very hard to install though.

You monster.

For those that remember Google Notebook, this is also what Evernote did 10 years ago. It's why I've been using Evernote for 10 years and why I'll never use Google Keep.

https://www.cnet.com/news/evernotes-google-notebook-importer...

The composition of the result of the original hash function and the result of that validation function can be taken together to be some larger function. Call that an uberhash. Such an uberhash is created by putting some number of bits in and getting some smaller number of bits out. There will unfortunately still be collisions. That trick is an improvement, and newer hashing algorithms contain similarly useful improvements to make creating collisions difficult.

I've had an Orbi for some time now. What sold me was that it doesn't actually create a mesh network. Instead, it sets up a 1.7 gigabit wireless backhaul connection completely separate from the frequencies used by the client devices you connect. This avoids all of the interference (noisy clients disrupting the access points) and latency (hopping from one access point to another) pitfalls you often encounter when using a traditional mesh network or wireless extender.

The Orbi is basically the wireless equivalent of running wires through the walls.

If that's true why do I see so many developers using Macs? There are lots of developers who use Apple hardware with linux. Even Linus (at least as of 2012)! http://www.cultofmac.com/162823/linux-creator-linus-torvalds...

Desktop Linux is a mess and always has been. The problem is structural. The people making it don't have any profit motive to make it better. They're all either volunteers having fun or subsidised by server products.

It sounds like you are saying there is a direct relationship between the quality ("betterness") of software and a profit motive to create that software and that there is no profit motive to make Desktop Linux better. I see two flaws with that argument:

1. You posit that there is zero profit motive to make it better, then there should be zero quality of the Linux Desktop. Certainly, you can't be saying that there exists nothing worse than Desktop Linux, even conceptually.

2. This argument, if I understand it correctly, also implies that it's impossible for an application to be "better" or "good" that has no profit motive. This would include all of the open source utilities, text editors, programming languages, compilers, games, emulators, and other applications - many of which ship with every single Mac on the market.

Those two reasons make your argument logically inconsistent, I think.

But, even if your argument were logically consistent, I believe that there is a profit motive to make it better. Some people, including myself, derive non-monetary profit from building something useful and we find that the open-source model allows us to collaborate on these things because they are too complex or time consuming to do alone. The fact that there actually exists a profit motive makes your argument factually inconsistent as well.

So long as one executor is executing the recipe/procedure/etc it makes sense to simplify directions to make them appear synchronous. When I turn my computer on and wait for it to start, I don't literally freeze up and stop breathing. I go do other things and wait for a signal that startup is complete or I poll the status of the computer from time to time. The synchronous instruction "wait for the computer to start up" is interpreted as "do whatever you want or need to do until the computer has started up".

As soon as two parties are involved, instructions start making sense asynchronously. Try writing a recipe for baking a cake by two bakers, keeping both chefs occupied the entire time. You'll see that the instructions must be read asynchronously otherwise each baker would not be able to continue reading his/her instructions when a "thread" of operation for the other baker has been called out.

Syncthing doesn't reconcile differences. Instead a copy of the file is created.

  Syncthing does recognize conflicts. When a file has been modified on two devices simultaneously, one of the files will be renamed to <filename>.sync- conflict-<date>-<time>.<ext>. The device which has the larger value of the first 63 bits for his device ID will have his file marked as the conflicting file. Note that we only create sync-conflict files when the actual content differs. 

Did Google? Google is very much a polyglot orginization. https://www.quora.com/Which-programming-languages-does-Googl...

As for Android, Google Purchased Android Inc in 2005, and I'm pretty sure the decision to use Java came before Google's purchase.

... And much of the rest of the code written these days: https://github.com/blog/2047-language-trends-on-github

If we're talking about the JVM, we must also include Clojure, Scala, Groovy, and any other JVM language code that would be killed if the JVM died.

If we're talking about the language, then the majority of Android and its app ecosystem are included.

Most importantly, don't forget that Java the specification is an open standard with dozens of runtime implementations and 7 compilers (not counting Google's). And the primary compiler, Sun's javac is GPL.

https://en.wikipedia.org/wiki/List_of_Java_virtual_machines https://en.wikipedia.org/wiki/List_of_compilers#Java_compile...

This article is basically a corollary of the Robustness Principal, "Be conservative in what you do, be liberal in what you accept from others". In this case we're accepting certain dependencies from others and we SHOULD be liberal/tolerant of dependencies that work but generate warnings.

The whole postmortem focuses on a regular expression bug and how that bug was fixes and completely ignores the fact that if the home page becomes unavailable, the load balancer logic will shut down the entire site.