1,066 karma · joined February 28, 2017
So all old Dart code won't work now? This seems much worse than the Python 2 - Python 3 jump.
Some could. And others look at it and think "Python" or "JS" speed app. Oh. And harder to refactor/detect errors.
1. Go had a lot going for it when it came out (single, static, exe, memory safety).
2. Go's stdlib came with a lot out of the box. To the extent that you can write some fairly complicated code without touching a single library.
3. There was cgo.
Is it like calling Java from Kotlin (pretty) or C from Java (ugly)?
> The other thing to consider is that this advantage of code reuse was never realized to iOS.
iOS does interact well with C.
And I don't think that anyone hates Dart because it has generics.
When Android came out, it was able to piggyback on millions of existing Java packages (such as Apache commons). When Kotlin came out, it was able to piggyback on millions of existing Java packages and Android packages (and even better, existing Java code can seamlessly forward work with Kotlin).
Now, Google is using its muscle to drag everyone to its language which has pretty much no existing adoption.
Oh. And many remember Dart being optional-typed (like Typescript).
So, while Samsung may ship Tizen and Windows Phone, they may not build phones for Amazon (which caused Amazon a lot of problems back in the day - where will you find a company making portable electronics that will make them a white-label product and not making android phones).
2. MicroG depends on Google's servers, so Google can pull the carpet out of them at any time. And where will you get those millions of apps if Google doesn't let you access the App store? Look at the difficulty Amazon has at getting apps into its store, and it's a larger company willing to pay devs to switch apps to Amazon store. And all the hacks that people use will be closed by Google once they get popular.
Now sure, you can use MicroG as a porting library (so if I have a closed source app relying on firebase I can trivially switch to relying on MicroG and Mozilla's back end - kind of like wine), but you'll still have to recreate all of Google's apps anyways (there's no way Google will publish their apps on an Android fork) and also those apps written by those who don't care to port (unlike wine - where I can use the OEM CD or EXE from the OEM website, there's no official way to get apks out of Play Store)
But it won't help if the bootloader's locked
Small question: Do people still buy $800 phones, and why? If you care about security, these probably won't receive security upgrades for more than a few years (S3 went from ICS to Kitkat. S4 went from Jelly-Bean to Lollipop, S5 went from KitKat to Marshmallow, S6 went from Lollipop to Nougat, so I don't expect this to make it past Android Q[1] (which should come out in two and a half years)), and unlike older models, custom ROM support is quite bad for modern Samsung models (S6 Lineageos just came out. S8 isn't supported yet).
Wouldn't it make more sense to get a slightly worse quality phone, but upgrade it every two years or so?
[1]. Unless Treble will make it so much easier to port to S9.
Really? How many programs supported Linux before electron?
Another idea is that when wasm will be able to interface with DOM, you'd be able to write GUI code in any language which compiles to wasm. So you won't _need_ Rust (or Go, or Haskell, or D, or your up and coming toy language) bindings for win32, Qt, GTK, etc. Just waste a few hundred megs (only partially /s) and you've got a full ui.
Oh, and that one is practically designed around a hybrid C++, so if you don't like C++ (last time I tried C++ with mingw on Windows I had a horrible time installing libraries), you're out of choices.
So now if google changes the back end, websites will slow down, which means that Google has to ossify implementation details, furthering this sort of black magic into CS lore forever.
This, honestly, is what I hate with modern dev. A few days back there was a discussion on how programming is hard nowadays.
Really, programming is more accessible than ever. What is hard is the "black magic" that's becoming more and more prevalent, most of which is implementation defined, that everyone is expected to know (and really, most don't really know anything. They just repeat rumors they read about online, often years out of date).
The problem is that neither your install or recover CD won't have it enabled by default, so if you have a problem, your hard-drive won't mount.
You can't edit while wasting time on the computer. You have to actually go to places you want to add. It makes scaling hard.
Look at it this way:
What do I want to see?
Friend's image/text > Group image/text > Pages I like image/text > Friends of Friends image/text > Memes > Ads.
What does FB want me to see?
Ads > Doesn't matter.
So what do they do?
Ads > Memes > Friends of Friends image/video Pages/Group Image/Video > Friends Image/Video ------------------> Text.
Why? What financial incentive do they have to show me Memes over what I want to see?
It could get worse. Since at that point, the Sun is smack in between the earth and mars, so for a few days you can't get _any_ signal through.
You'd have to bounce it off some third satellite in solar orbit (like a triangle).
They still want it back for data.
The thing is that there would be no point in doing so (which, admittedly, hasn't stopped Google before).
Right now Google needs WordPress. Without WordPress, where is Google going to place ad spots? Facebook? And WordPress has PHP as a massive underestimated advantage - every Tom, Dick and Harry can spend 5 minutes to install WordPress on a $5 a month shared-hosting plan, something no Ruby/Rust/Go/Java/C++/Node/Erlang/Fashionable-Language-Of-The-Week can do.
NASA recovered rockets and landed on the moon years ago.
What they didn't do was lower the cost to orbit.
_That_ is SpaceX's thing
People were able to kernel panic it, get privilege escalations, and DDoS it. In short, it had the same same issues a C based kernel would get.
It's true that it's still heavily in development and doesn't offer any guarantees whatsoever, but I think that it should be pointed out that just because your language is good, doesn't mean that your end result will be good (and vice-versa, C based kernels like l4 and C based projects like SQLite have been formally verified (at least SQLite was verified after compilation, so they check for undefined language constructs.))