8,592 karma · joined March 30, 2014
In contrast, Australia and Canada both have Westminster parliamentary systems, where the executive is drawn from the legislature. Thus, the prime minister is guaranteed a base of support there and populist candidates cannot entirely circumvent it. The system has its flaws, but it does seem to be more stable in the long run.
A negative comparison often seems to be made between software engineering and construction, but it seems to me that the latter is a unique subfield of engineering, where you have an unusually large number of projects with a roughly homogenous set of constraints and variables. This has allowed those constraints and variables to be studied, understood and mastered to produce a discipline that more closely resembles mass-production. And in those subfields of software that also involve more homogenous constraints, such as the production of standard commercial websites, you do see a more controlled and templated approach, using tools like Wordpress.
[1] https://www.power-technology.com/news/neoen-to-build-300mw-b... [2] https://en.wikipedia.org/wiki/Neoen
> I doubt that a programmer who wouldn't spend $100 for a font would spend $5
This is where we disagree then. I think there is a big psychological difference for most consumers, including devs, between spending $5 and $100. Even if you can afford both, the former falls into the range of impulse purchases, like getting a sandwich or a cup of coffee, where you spend without really thinking.
On the other hand, I think a $100 price is far more likely to trigger a more analytical and skeptical response. Do I really need it? Is it worth it? Should I research alternatives? Maybe, I should think about it and decide tomorrow... Etc. And the consequence will be a huge drop in sales.
Also, I also do think there are significant differences in the market for programming fonts vs. general desktop fonts. The market for a single font is likely a relatively small pool of designers / content creators who are spending their employers money, need it to complete a specific project, and who value achieving a unique look. The former is a larger market, who are spending their own money on a nice-to-have, and who don't particularly care about uniqueness.
On the other hand, if these fonts were priced at around $5, they drop into the range of an easy, impulse purchase. Even if the creators made substantially less money on each license, I'm sure they'd make more overall from much higher sales.
The article I will take as a single data point, about one person's experiences. But comments like yours, and others in this thread, worry me far more. Collectively, they exhibit the dismissiveness, defensiveness, condescension and victim-blaming that is absolutely typical of members of religions/cults both spiritual and secular. Anyone who can describe the experiences related in this article as "desired and welcome" has lost any sense of perspective.
If you're a a medical startup, having an off-the-shelf prediction model you can just start using for all your protein folding needs is a very different proposition from having to train one yourself from scratch.
That said, hopefully other researchers and institutions will take Google's research and produce an equivalently powerful model but with a more commercially-friendly open-source license. From some comments in this thread, it sounds like that's already happening, in fact.
> As of 18 June 2021, according to DeepMind's CEO Demis Hassabis a full methods paper to describe AlphaFold 2 had been written up and was undergoing peer review prior to publication, which would be accompanied by open source code and "broad free access to AlphaFold for the scientific community"
I don't know whether crime in SF has gotten worse or not, but as a resident of a city where people don't defecate on the sidewalk, it boggled my mind a little to see someone apparently advocating for the city on the basis that sidewalk defecation wasn't a new problem.
But since React is a such a minor part of the JS/TS landscape, who can really blame the TS team for not prioritising this, right!?
And while backwards compatibility remains a concern for browser vendors, it's much less of a concern for web developers nowadays given the vast majority of users are using auto-updating browsers. Indeed, the purpose of this guide appears to be an explicitly "evergreen" guide to CSS, targeting only the feature set of modern browsers. If you're using grid, custom properties, conic gradients, etc. you're not writing backwards compatible code.
And politicians seem to really love it as well, perhaps because it is a funny-sounding, non-threatening word, implying a minor hiccup rather than a serious defect. So, whenever some new, high-profile software system crashes and burns upon launch, you get lots of folksy talk about glitches: there's just a few glitches, they're fixing the glitches, you've got to expect a few glitches, etc. Whenever I heard such talk, I like to imagine the difference between the attempts to downplay the problems, and the likely reality of stressed-out engineers scrambling to fix a system that was released in a half-finished state due to an unrealistic deadline.
"The contract makes clear the Commission and EU countries can't sue the drugmaker for a host of issues, most notably if there are 'delays in delivery of the Vaccine under this Agreement.'"
[1] https://www.politico.eu/article/coronavirus-vaccine-europe-c...
Personally, while I'm not on board with the board with the direst predictions of the super-intelligence pessimist crowd, I have become more and more convinced that goal misalignment is going to be a significant problem, and that while it might not doom the species, it's something that all AI researchers like Hawkins need to start paying close attention to now.
This would be have been fine, so long as these systems remained relatively simple, and were rebuilt in more heavyweight but scalable languages once they reached a certain level of complexity. But that isn't what happened. Instead, they just kept growing into twisted, unmaintainable monsters that organisations were completely reliant upon, but which were an absolute nightmare to maintain and extend.
As a result, the industry shifted to encouraging the use of "real" programming languages for everything, even the simplest systems, because the greater up-front costs were saved many times over by having a sane story for long-term maintenance and improvement.
https://www.politico.eu/article/the-key-differences-between-...
The conclusion, at least as I interpret it, is that both the UK and the EU can reasonably claim to have priority, based on their respective contracts, but that the UK did a better job than the EU in making theirs enforceable. Hence, AstraZeneca has prioritised them, while the EU has been forced to resort to political rather than legal measures to attempt redress (publishing the contract, export controls, etc.). And the UK's closer ties to the AstraZeneca vaccine project likely did mean they started work on the UK supply chain somewhat earlier than in the EU, even although the final contracts were signed essentially simultaneously (one day apart).
I honestly don't really see this as an affair with clear good guys and bad guys, but it seems like most people are determined to do so, and inevitably along the lines of their pre-existing sympathies.
But what I'm suggesting would be a functioning regulatory regime: An independent authority who classifies cloud providers as utilities, writes regulations specifying standards of interoperability, hears complaints from people and businesses and acts to enforce them. Antitrust regulation that stops collusion between service and application providers, and prevents companies or individuals owning a controlling stake in both.
And the major difference I see in contrast to railways is digital infrastructure is not limited in they same way physical infrastructure is. So long as there's only one set of tracks, you can never have a functioning market running trains on them, and it's impossible to build a second set. But while the capital costs of setting up a new data centre are large, they are still within the realm of possibility for many large companies.
As I see it, cloud providers are currently entrenched as Lords of Everything because they can both provide the infrastructure and the products that run on top of it. Making them act more like utility providers would reduce their power, I think.
I'd like to see an enforced separation in law between commercial application providers and storage providers. So, if someone writes an app like Google Docs, they can't just store the data opaquely on their own cloud servers. They legally have to integrate with a separate storage provider. And that storage provider has an obligation to make my data accessible and manageable by me.
This wouldn't be a panacea, but it at least makes it theoretically possible to write a replacement client for Google Docs that could be a drop-in replacement.
If it's so dumb for anyone to even ask if three explosions is a problem, why did you do this? Why didn't you just write "Asking if three explosions is a problem is a dumb question to even ask."? Why was it necessary to introduce supporting evidence?
Could it be that you think it's a dumb question because you know these facts? And the article author's job, as a journalist, is to assume, accurately, that most people don't know these facts. Most people are not SpaceX super-fans who have been closely following the test programme. Many will just hear "SpaceX blew up a third rocket" and wonder if things are going wrong, and the author's job, as a professional journalist is to inform those people.
This hypothetical browser wouldn't perform type-checking, just be able to parse TS syntax and convert it to plain JS, in the same way tools like Babel do.
This would let you use TypeScript without the need for any transformation pipeline in dev. You could then separately run TypeScript in a console to get async checking. Then only when you build for production do you run everything through a compiler/bundler to get a plain JS bundle that will work in everyone's browsers.