matzipan

elementary OS has evolved a lot from just a simple skin on top of Ubuntu. You can see here [1] all the projects which are maintained by the team.

[1] https://launchpad.net/elementary

The argument is that the potential user needs to be aware of his action when he's entering in "0". Otherwise, it's just automatic - you don't even think about it.

I've had similar issues with Haswell and the Intel 7260 wifi card when it came out. It was fixed, but it took over a year after it was relesed :(

I presume you know about Matthew Garett already? http://mjg59.dreamwidth.org/41713.html

It's certainly on the to-do list, but some features related to swipe were implemented in the GTK version after than the one Ubuntu 16.04 LTS currently ships, so it'll take a bit more time.

I personally want that feature too.

Mail used to use webkitgtk (the old api), but has been since ported to use webkit2gtk (the new, multi-process api), you might wanna give it a second look.

EDIT: I stand corrected. This has not happened yet. I confused this with some other changes.

Exactly! For example, Skylake support is not mature enough in Linux atm.

The AppCenter is the hottest development area, so there are new features and fixes landing every day. But in the not very distant future you're going to see the result of a lot of work: https://houston.elementary.io/

There is a problem with Epiphany, namely that the webkit version that ships with Ubuntu is long outdated, hopefully that's going to get fixed: https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-secu...

True. I guess this paranoia is coming from all the manufacturers just willing to rip everything off.

Why does the foundry need a license too? I just give it a mask! That sounds like IP hell.

Do you guys do summer internships?

My degree should be proof that given some time to study I am capable of implementing it.

Applied for Thales UK a few months ago. I was met with 19 pages of personality quiz. Seeing that, I decided I don't want to work there anymore, but I dared myself to finish that questionnaire. It was excruciatingly painful and felt really no regret when I was rejected.

The 960 day github streak is an illustration of his passion to code, of the fact that he is doing it for the pleasure of coding. He said it himself that it's not there to show any skill.

Why does Uber require scale to return profit?

There is no way in hell that loss is going to turn into profit this millenium. Unicorn valuation is basically a very expensive game of hot potato.

Uber thrives?

Wait, so is this HyperContainer thing, like... a virtual machine?

This reminds me of the computer collection one of the lecturers in my department owns (http://www.computermuseum.org.uk/). They have quite a number of historical pieces finishing with a number of Crays, an IBM Blue Gene a few nuclear plant control units.

It's called a Chromebook :P But I do get what you mean

Forgot PNG is lossless :P

You have a point. But I also like fast, snappy websites :P

It was not born out of necessity. It was born because of the way your brain percieves the images. There is no need in adding detail if your brain can live happily without it.

And if FLIF achieves such great lossless compression, imagine what amazing compression you can achieve with lossy compression.

How often do you need lossless images on the web? Almost never.

More like app ecosystem.

Does anybody understand how lossless JPEG works? To my mind, the whole point of JPEG is to get rid of high-frequency components.

That's most of human nature you're describing there.

My argument is that you'd have cross-distribution appimage maintainers who would press a button and rerun the build script with the new library if it's needed.

I've been spending a lot of time in the embedded area lately (sub-200Mhz 32k RAM automotive systems, firmware and fpgas) and I agree with you. But there's always tradeoffs. In this case you're trading some memory (which is cheap nowadays) for up-to-date, secure, usable apps, which seems to be a pretty complex thing to do. Nobody solved it so far. The people using node-webkit are offloading the library compatibility issues to the people who built Chromium and are provided with a consistent container to run their application in.

I believe Ubuntu has done a some progress in this area with Snap packages.