https://events.google.com/io/schedule/?sid=fed907cf-4b51-433...
https://events.google.com/io/schedule/?sid=496d01fb-2139-4fd...
Disclaimer: I'm in one of the talks.
You can use Flutter today to write an app that runs on iOS and Android. :)
On one hand, the website says that it's compiled to native code (so it can be same speed/faster than Java), but on the other hand, it's based on a soft-type language, which makes optimization difficult (even with V8, JS is still slower than native code).
Side question:
I understand that Dart was soft-typed because it was supposed to replace/compile to JS, but what advantage does soft-types have against "implied-types" (like auto or go's := ) combined with operator overloading (to allow string+int, for example)?
Recently Dart has added a strong mode (https://github.com/dart-archive/dev_compiler/blob/master/STR..., http://news.dartlang.org/2017/01/sound-dart-and-strong-mode....).
One of the reasons for strong mode is to enable better optimizations (https://www.dartlang.org/guides/language/sound-faq#why-stron...).
When JS performance threads come up I always mention that JS will never be as fast as Go/Java. Some people have a tantrum when I explain these issues. The sources I usually cite are dense and people just continue to downvote without reading them.
I think it's a work in progress, but main benefit at least at the time was faster startup.
Unlike the script snapshots, application snapshots also include CPU-specific native code in addition to the serialized token stream of the source code.
So, you don't just skip the parsing stage, you also skip the warmup phase. Your application starts instantly and it runs at full speed from the get-go.
I didn't find a doc on how low level is this framework going. Or to put it differently , where does it plug itself on the iOS stack ? opengl ? calayer ? uiview ? webview ? etc...
It's fairly low level. It uses Skia, which is a 2d rendering engine Google bought 12 years ago that powers Google Chome / ChromeOS, Android, Firefox and Firefox OS. Skia is built on top of OpenGL, but they've been working on a Vulkan backend that is close to feature parity.
This seems to be how they get the high performance animations. It also explains how they are able to do cross compatibility between devices (You really only need C++ and OpenGL).
Here's more info from their FAQ: https://flutter.io/faq/#what-technology-is-flutter-built-wit...
Dumb question, does this mean that it's limited to software rendering only? You need to go through the kernel to talk to the GPU, right?
That's sort of the whole point behind Mantle/Vulkan/Metal/DX12.
In the cases where it does, I imagine it's a situation where you're actually doing 3D-accelerated renders of the user interface. In which case, when the graphics subsystem craps out, hasn't your running system been rendered effectively unusable anyway?
I get that this is a nice idea in theory, but does it actually improve anything practical in practice?
If not, how exactly do you plan to restart the graphics process?
ssh from my phone and restart the driver.
Go to a fallback ui, and restart the driver.
Have a system util notice the driver is misbehaving incorrectly, and restart it.
Then there's the whole "GPL mafia" in the Linux world who'd like to force vendors to open up their drivers by moving as much of the critical pieces to the kernel as possible. In theory, you cannot write a kernel driver without violating the GPL. Fuchsia will have no such impositions. If someone wants to open their driver up, they could. If they believe their offering is superior, and a secret sauce needs protecting, they can keep it closed
Do you see many vendors being forced into change?
AMDGPU is already very usable. I remember ~5-10 years of waiting to use my Radeon 9600 with a recent kernel until the free Radeon driver was finally up to snuff. Catalyst and fglrx were awful.
Proprietary drivers just don't make sense. They are practically unmaintainable.
For non-GPUs, only some WiFi drivers are out-of-tree (Realtek and Broadcom).
Sure, it is, for lots of people. Even, apparently, the FSF, hence the reason non-consumer products are not subject to anti-tivoization rules in GPLv3.
Both the PS4 and the Nintendo Switch run on FreeBSD, by the way.
Not exactly from what I've read, the PS4 runs 'Orbis OS' which is based upon FreeBSD 9, meanwhile the Nintendo Switch is using the network stack from FreeBSD, but also stuff from Android and the custom OS they wrote for 3DS.
Some businesses feel threatened by some open source licenses and other businesses are using the same open source licenses to do the threatening.
The funding for many important open source projects comes from global corporations that use it as part of their strategy, sometimes dominating entire industries based on open source.
A large number of small consulting businesses are based entirely on open source software as well.
Open source is not meant to be anti-commercial, nor would that make any sense, because "commercial" is what most of us do to make a living. That is not what takes away anyone's freedoms.
What does take away many freedoms is the fact that none of the widely used open source licenses fulfill their original purpose.
Linking rights to distribution once meant that users of the software got those rights. Now, in the age of the data center, end users get no rights at all and software can be modified freely by those who run the data centers without granting anyone access to those modifications.
Software has become more opaque than it has ever been before since the dawn of the PC age. Even without access to source code we had more control over Microsoft Excel than we now have over anything that runs in a data center, regardless of whether it is nominally "open source" or not.
> They aren't writing a new OS,
> at least, not in the complete sense.
Neither was Linux. It was based on Unix.Neither was Unix. "The success of UNIX lies not so much in new inventions but rather in the full exploitation of a carefully selected set of fertile ideas . . . " --- Dennis M. Ritchie and Ken Thompson, "The UNIX TimeSharing System"
OR it could be a UEFI experiment...
"This project contains some experiments in software that runs on UEFI firmware for the purpose of exploring UEFI development and bootloader development." -https://github.com/fuchsia-mirror/magenta/blob/master/bootlo...
Building user land OS's is a fascinating (if not new) idea that I really love to tinker with a myself. It really would be nice if they can pull it off.
Read through what I could find of the IPC code a while back. Currently it seems workable but a bit "baroque", then again if, as you say, it is working inside Chrome, I guess it is battle tested.
Messaging has always and still is the future for very loosely coupled systems, and driving it all the way down would be really great.
Been following this for a while and can't wait to give it a whirl. Plus everyone likes to root for shiny new OS design projects.
Are there concerns on non-dedicated graphics cards, or running say an ARM-based processor.
Also I'm not sure what you mean by '...easy to compile...' How do you compile this? I'll have to read up on it. Get that checksum bruh.
I remember trying to use Slackware and for me that was a lot of work.
Edit: Oh I see at this time it is limited to three physical machines. Interesting on the Pi 3 part. I wonder if I could try it in Virtual box. But why try it in the first place?
Moore's Law. Give it another decade and it'll be Etacs.
Compare using VS Code w/ Typescript Language Service to any type of dev stack that includes the word “Scala.”
Open VS Code and then Sublime and be amazed.
Atom and VS Code can never be 'easy on the memory' because they have to load an entire Electron instance just to idle.
At what? Using 5% more total resources? Great tradeoff!
I have significant experience with all big Java IDEs, 3 months full time with Visual Studio (in addition to testing it on and off for years). Use Sublime regularily. Can use vim productivily for server config. Have used emacs enough to get a taste of it.
But lately I find myself getting back to NetBeans whenever possible, not because of price but because of features, sensible defaults and stability.
OTOH, my hobby programming is done on an HP Mini 101.
It's easy to use, but it's not easy to learn.
(I personally alternate between both Kate and Vim, depending on whether I'm in more of a GUI or a CLI mood)
They are using the IPC system developed in and extracted from Chrome. They are drawing everything in userspace with fast graphics render but the logic for all system components written in Dart from the Flutter project. They use musl for the libc. They are using the little kernel for the core kernel.
As a long time Linux desktop user myself, I'm really excited about this project. A secure desktop without tons of system calls? Userspace graphics? Not HTML/JS based? But could still be used for development? Yes Please!
It's really easy to compile and get it running. Try it out!