2,111 karma · joined February 20, 2010
In fact, many "normal" phone apps are basically just a web-site inside a thin wrapper. So the difference is largely academic in many cases.
It's hard enough to get programmers to care enough about how their code affects build times. Modules make it impossible for them to care, and will lead to horrible problems when building large projects.
If they are not releasing their sources, because of inappropriate licences, then that's what licenses like AGPL are there for.
I've got much less of a problem with AWS making money than I do with Canonical replacing GPL code with knock offs designed to cut the community out of code sharing.
TikTok is much closer to how YouTube started out.
Given that they apparently have no new models in development, I'd expect the latter.
- Their roadmap is just updates to their existing line-up, and vapourware crap that relies on their "Full Self Driving" somehow magically starting to work.
I suppose it's good that these people actually bother to read the license and intend to respect it.
> Under this relaxed definition, we find that we cannot establish a total > order over all memory_order::seq_cst operations due to a cycle in the graph: > (2) -> (4) -> (6) -> (7) -> (2).
I don't understand why they say that "(2) -> (4)". (2) must certainly come before (3) in the context of threads 1 & 3, which both refer to X and Y. But thread 2 knows nothing about X, so AFAIK accesses to X can be arbitrarily reordered from the perspective of thread 2 - if "reordering" can even be said to have any meaning at all in a thread that knows nothing about X.
> "[solar] adds $20,000 - 25,000 to reroofing a house"
Since all of the scaffolding or whatever is already up for the roof work, if anything the solar ought to be cheaper, in that scenario.
Even the example used on the blog post is wrong (in my timezone)...
Start = date(2020-02-23) End = date(2020-04-05)
Duration = End - Start // 42 days Duration as hours // 1008 hours
2020-03-29 was the start of Summer Time, so only 23 hours long. So the duration in question should be 1007 hours.
Having a span of time using days as the only unit is fine. But there no way to convert that into a different time unit without knowing which specific days we mean.
What happens if the duration concerns something that physically moves? Was the software running on a ship that travelled from Europe to Australia between February and April?
Honestly, gushing about how dumb everyone else is, without mentioning even basic wrinkles like this just screams Dunning Kruger.
Why do you need two electricians for a week? My rooftop solar array went up in an afternoon. They had three labourers. The (singular) electrician came in separately and worked for under and hour.
In all honesty, I thought I was being clever by swapping the sentences around to reverse the meaning, but I didn't spot the ambiguity.
Fixed that for you.
Also, having your library rely on static initialisation doesn't seem like a very sound architectural choice.
Honestly, this just sounds like whining from someone who can't be bothered to read the documentation, and can't get the coders to take him seriously. In the time it took him to write that article, he could have read up on his tools, and probably learned some social skills too.
That seems like it's a much greater benefit than the reduced walk-times.
For sure social media is propagating conspiracy theories, some of which are the modern equivalent of "Saddam can deploy his WMD in 45 minutes", but I don't agree that old media was doing the same. Quite the opposite.