Re: Edinburgh Uni and Standard ML
+1 one for quiche eaters.
We lived on the vending machine, or ordered chinese food.
32 posts • joined 4 Nov 2016
Just because you're not doing the 'hard' stuff, if I see 100 copy/pasted expressions with minor changes, I can assure you I am going to slaughter you during code review.
Don't EVER write the same code over and over. If you can't abstract properly, you're chalking up technical debt that will choke even 'non hard' projects down the line.
Intellisense is handy, it lets you trivially explore an API from the keyboard, helping you to remember that function name, or browse through and find functionality you didn't know existed.
Emmet-like templates are handy for managing boilerplate (although much better to have sensible refactoring tools).
I am perfectly capable of writing my own bugs. I have, in fact designed and implemented inductive programming algorithms, and the topic is an active interest of mine. I can assure you the state of the art does not even consider "throw it into a big pile of linear algebra and predict n-grams". That is stupid.
They are doing it *completely* wrong.
Certainly you could actually do a much better job of compiling JS to V8 if you want to spend some time in an optimizing compiler.
Unfortunately because Spectre popped up, we no longer have access to SharedArrayBuffer. This means you cannot do concurrent garbage collection, so your overall performance would tank hard.
It's annoying but I'd rather not leave my keys in the dash.
Is their any evidence Microsoft has rehired more QA staff, or are they just locking the remaining 5 in the office over the weekend?
Certainly looking at the facepalm inducing but otherwise increasingly irrelevant electron rewrite of Skype, the answer is no.
Curious what evidence exists to suggest Microsoft quality hasn't dropped back to 2000's vintage. Rather like Apple. Anyone got a Linux dvd I can borrow?
On the other hand, Facebook shares are higher today than they were before the CA scandal. I'd love to believe their days are numbered, but to a shareholder, the ability to give everyone the middle finger is a positive attribute. No long term damage happens. Nothing ever happens.
This post has been deleted by a moderator
I fscking hate autoplay on most sites, but as a developer I would strongly make the case where games and video sites are an obvious scenario where a user would happily whitelist this capability where necessary, much like you can whitelist video capture, geolocation data or myriad other features.
Autoplay is one of those features that is *really* useful for a narrow class of popular websites and applications, that has been horrifically abused by everyone especially mainstream news sites.
Now we have a botched solution that looks like it will suck for both end users and developers, breaking sites that will need it up front, and letting idiots through the net. This is why we can't have nice things.
If you have 50+ tabs loaded on your desktop every single one can be running setInterval scripts and chewing up your CPU and battery. This is true for iPhone or desktop, so that isn't really any different than now. Lots of tabs open is still lots of tabs open. And lots of sites are written by idiots. Sadly there is no W3C working group for making people write less shitty code.
Service Worker background scripts are VERY limited in scope, and can't just quietly sit in the background mining bitcoins- the browser is supposed to kill them dead if they execute too long. Like any browser feature, if you don't like service workers in chrome, disable them in chrome://settings. I am sure Apple will provide a similar option. In general, judicious implementation of PWAs should *decrease* your battery and network consumption over standard browsing (things like the fetch API provides a customisable transparent network cache for the app, and the ability to drop offline in crap network conditions where you would traditionally be re-transmitting corrupt packets).
Surely, service workers are far, FAR less of an attack surface than visiting a site, downloading their freaking binary from an app store with myriad more ways to punch into the kernel, which is the current state of affairs. All that for yet another glorified RSS reader. End users don't even think twice about doing this, and they have moved potentially malicious code through the bulkhead of a browser sandbox, and into a direct user space process.
Unfortunately I agree, the way many sites are adopting service workers is simply to nag you with push notifications, but 90% of the web is shit, and this is just another example of it being shit. Don't like being bugged to install push notifications on a site? Don't visit that site... Long term PWA provide scope for moving beyond Apple's walled garden iTunes store, where Apple skim 30% of *all* sales through your app, and will pull your product from the app store because it mentions there is an Android version.
Sure, like all technology there will be security issues discovered, but just like WebGL when everyone was losing their shit and Microsoft claimed it was far to insecure to implement, fast forward five years and every major browser (even Microsoft's) has an implementation and there hasn't been a string of exploits for WebGL subsystems released every other month like we had with Flash and Java.
As a freelance developer, market share means nothing to me. Developing an App costs money, and those who invest in these hope to get their money back. Even if Apple's market share drops to 1%, if fanbois are 101x more likely to whip out their credit cards, then iOS is still the only sane business decision from my clients point of view, and thus we all still have to put up with Apple crap.
Biting the hand that feeds IT © 1998–2020