> Spam filtering is a a very difficult thing to do well and Google's implementation was very good, very advanced, and trained on huge amounts of data. Something a normal person could never do on their own server
I'm sure most normal people could install SpamAssassin and configure it to use community blacklists on their Dovecot/Postfix server. It's not that hard.
I run a mailinabox server for almost half a year and gmail is a pita. I send an email to a gmail user and it always goes into spam. I have to phone them to unspam it but next day same thing.
Yahoo mail or others dont seem have this issue because I have 10/10 on the dkim something scorecard.
Google somehow wants to force me to not use my email server. Fuck them
Hm, personally I feel Google is cheating. While they catch also all spam they also catch a lot of legitimate mails. I have a couple of accounts at Google and one at a company which uses SoamAssasin and I prefer that SoamAssasin setup since it has way less false positives but still catch most spam.
Nice summary, but I dislike the fact that education has made the default understanding of these categories to be about retaining information/knowledge rather that your ability to compute/reason/intuit.
Yes, familiarity with a field should improve skill, but I like to think that one can be smart, intelligent or wise in a situation that does not involve previous information about it.
Someone exposed to a brand new game or puzzle can be smart, intelligent or wise in solving it separately (to some degree) from having prior information.
> Actually, my memory is essentially that the IE team was doing decent work.
Yes for a while there they were doing a great job of implementing Microsoft's Embrace, Extend, Extinguish philosophy by intentionally avoiding web standards conformance and instead focusing on proprietary features (ActiveX plugins etc) in attempt to make IE "better" than the competition
This is actually compatible with what I was saying. The ie team was building a decent product. If it was being sold, it would have been a healthy competitor in the field. Instead, the company pushed it for free to basically burn the market.
Reddit is still accessible on mobile via browsers though, so even if Apple imposes rules on the native app it's easily worked around. AFAIK the discord webapp only works on desktop, so for iOS users wanting to access NSFW discords on their mobile device they are shit out of luck
> Reddit is still accessible on mobile via browsers though
Barely. They’ve aggressively pushed the app on mobile users for years, and they keep moving more and more of the mobile site behind a login screen. For example, you must now make an account to view more than the last few comments on a post on the mobile site.
> I had to check that this wasn't an April fool's day post. Linux powers a large proportion of servers on the internet, and has done so for a long time now. The popularity of Git is a relatively recent phenomenon.
Linux might be used for the majority of web servers, sure, however Git is used for version controlling the significant majority of software produced today. I would argue something that is used by nearly every software development team/company across the entire planet has a much greater impact than something that is used by nearly every server across the planet.
Linux also sees more heavy competition from the likes of Windows and *BSD, where git has essentially dominated it's market with things like CVS, SVN and Mercurial becoming increasingly abandoned, and only niche proprietary systems like Perforce still competing for usage
It's got a big impact, but mercurial was released pretty much the same month as git. Git got more popular, likely helped by Linus already being known. If we didn't get git, we'd use something else without issues. And you can use something else right now. Linux on the other hand just doesn't have an alternative equal in features.
I'm not sure I agree. git has a particularly lucid underlying data model which is the reason why it has endured so long (despite its objectively awful ux), and still sets the bar for cryptographically secure SCMs.
"Heavy competition" is overselling the threat that Linux faces from Windows in the Internet server space. I'd go with something like "Linux roundly dominates, save for some legacy environments that have largely been picked off by cryptolocker breaches over the last several years."
> Linux also sees more heavy competition from the likes of Windows and *BSD,
No it doesn’t. Neither of them are even a consideration in most server scenarios at tech companies. Anecdotally, every company I’ve worked at used Linux in multiple forms (severs, embedded, etc) but not all of them used git (Google is the most well-known example).
Every tech company I've worked at used Linux for servers as well, however that doesn't mean I'm ignorant of the huge number of (predominantly large enterprise) corporations relying on the Windows Server stack. Also I would argue there are significantly more servers, embedded devices and especially networking infrastructure running *BSD than you give it credit for, not to mention every consumer device manufactured by Apple.
How many open source projects or tech companies can you cite using an SCM suite other than Git, except for Google which you already mentioned?
The huge disparity in usage makes it pretty clear Git is the only widely relevant SCM suite today. GitHub and GitLab are arguably the most active and central hubs of open source communities, and they're based on Git. Bitbucket discontinued Mercurial support a while ago. How many popular / impactful public code hosting repositories are primarily using SCMs other than Git? I'd be surprised if you can name a single one other than Google's now discontinued Google Code service.
It depends on your success measure. There are way more Android users for example (most smartphone users), or people who interact with Linux servers (basically every person on the www), than people who use git (developers, a niche profession). The first two categories contain billions of humans, while the last category includes maybe a couple dozen million or so.
I really do not understand the appeal of Svelte, it seems to be making all the same horrendous mistakes as Vue (bad templating/DSL that shoehorns control flow and bindings into DOM representation, esoteric lifecycle hooks etc) and the only advantage it clearly has over other frameworks that I can see is simple components can generally be written more concisely.
Are there actually any tangible benefits to using it over other frameworks, or is this all just a heap of people getting excited because it's "new and shiny" (compared to React, Angular etc)?
- Instead of virtual dom + diffing, svelte applies direct DOM manipulation exactly where needed
- Smaller code size. No loading of general runtime library, and I've heard people argue that each component(or page) has its own runtime (I may be wrong in the details)
- Many common tools are built-in, like stores and animations, and since there's no general runtime, if you don't use a particular tool, it doesn't get included
- For beginners, the tutorial is a blessing, they can pick up the framework while learning Js on-the-fly (I'm doing this with my nephew)
Smaller code size only applies for small projects. Preact is like 4kb (I believe you could print off the minified source on one side of a sheet of paper) and most full vdom implementations are still only 40k or less over the wire.
Once you have the runtime, it’s a fixed size. In Svelte though, every new component must carry not just the description of changes, but also reinvent the wheel by reimplementing each time. How many components do you need to reach 4K or even 40k? Even a small app can easily reach the size inflection point.
Also note that inlining code works differently in a JIT. Your code must run hundreds of times to be optimized. In a vdom, that is done almost instantly for all the most critical render code paths. In contrast, infrequently used svelte components are never going to optimize. This has the effect of making svelte look very fast in micro benchmarks which run the same few components repeatedly, but doesn’t reflect your performance when the user opens up something different and winds up back in interpreted mode.
Preact is a nice middle if you’re concerned about garbage. In addition to being tiny, it diffs against the DOM directly instead of using a vdom.
I would argue requiring your whole team to learn a new framework-specific templating language and patterns is not simple, compared to using something that is plain JS/TS which the whole team already knows. It also complicates hiring, as programmers who know JS/TS and can pick up React/Angular/etc are a dime a dozen, in contrast to trying to hire programmers to work with a niche framework which has a lot of domain specific knowledge.
Pretty standard Microsoft strategy really. Once they decide they dominate a market they figure there's no reason to invest another cent into improving their product offering. See also: Internet Explorer
What I would find really interesting is if someone used this exploit to hack into the accounts of Sakari staff and sabotaged their service, deleting all their infrastructure from their cloud hosting provider etc. I'm sure Sakari would take this security hole more seriously if their own C-suite fell victim to it.
> I wouldn't be surprised if the business had been able to pay money to Google to be able to check reviews before they went live and mark them as spam.
I would be really surprised, as such a scheme existing without being exposed by now seems highly unlikely, and it would completely undermine the value of Google Maps reviews once everyone knows businesses can freely curate their reviews. Why would you bother looking up reviews for a business if you already knew any legitimate negative ones would be censored out? You wouldn't. Nobody would. Reviews on Google Maps would be discontinued by now if it were ever the case.
I'm sure most normal people could install SpamAssassin and configure it to use community blacklists on their Dovecot/Postfix server. It's not that hard.