469 karma · joined September 16, 2015
I'm a bit worried about putting too much into the "store" and their own browser, but so far it hasn't impacted me any. Anything that applies to Ubuntu proper applies in eOS for the most part, but the UX is just much more polished.
When I first saw it I was worried of too much "MacOS" like (which I'm not a fan of), but that has't been the case for me at all.
While a lot of the modern web is great, it also has drawbacks that should be looked at very carefully: A simple HTTP page from yonder can still be rendered just fine. A modern page can't be rendered properly a year or so down the line. We need modern protocols to solve modern problems we've created such as huge pages with tons of links and back and forth traffic to many servers. While I think work needs to be done in both directions, I don't know what we really need to go so far as to push down yet another HTTP/x protocol this soon. HTTP/1 is going to be used for quite a while still, HTTP/2 solves a lot, and where it matters (ie: dealing with specialized servers) QUIC is already and has been in use.
See http://telnetbbsguide.com/ (seems to be being funky right now) or self plug! https://xibalba.l33t.codes/
* CC generators actually worked to create an account that would last a good amount of time
* In the early days (~ AOL v2.5) they had a CGI form you could fill out and have a disc sent to your home. So of course we scripted it and had hundreds of free formattable 3.5"'s. A bit down the road and MS had a similar thing for Windows '95 replacement discs -- they'd send you the entire set if one was bad, which was a lot of good discs :)
* AOL at one point allowed ordering physical products (early digital cameras and the like) via your account credit. Mix in a phished account and you can see how that goes.
* I can't remember the names right now, but there were services in which you could pick up a CD and get free dial-up email access. The gig is they would show you ads. Patch the EXE and viola, you essentially just have a PPP account to the web.
There is no real incentive to change their behavior camera or not.
> and I'm not convinced that the "variety of reasons" are compelling.
I really don't want to be a jerk here, but you don't need to be convinced. If the general community feels a certain way, and you wish for said community to favor you, you must abide.
Don't get me wrong here, I'm in full support of a commercial version... but as you can see from the feedback here, this kind of thing is really frowned upon in the personal / OSS space for a variety of reasons.
I encourage you to re-consider added headers. Perhaps look at a more heavy handed download process such as the "Pay as you want" system used by ElementaryOS's download page (https://elementary.io/).
We are a family controls company focusing on solutions to children safe and parents at ease in the modern mobile world!
We have a relatively small development team and need to grow to meet demands. We are seeking full stack / DevOp engineers to work on a variety of projects such as replacing legacy backend systems, develop new client features, and expand our DCA technology.
Some of the things you'll play with: • Node.js, C++11, and a bit of native Android (Java) and iOS (Swift) code • AWS, large amounts of data, and hundreds of thousands of clients • Nitty gritty system level programming all the way up to UX • Work with a small team where YOU can make a difference
If you're an awesome developer we want to hear from you regardless of technology skill sets! This posting is listed as onsite, though we might consider remote given the right person.
Contact bashby(at)contentwatch.com
Keywords: ONSITE
⋊> ~/Downloads ./exa-linux-x86_64 --version 15:26:40 ./exa-linux-x86_64: error while loading shared libraries: libhttp_parser.so.2.1: cannot open shared object file: No such file or directory
...yup.
We are a family controls company focusing on solutions to children safe and parents at ease in the modern mobile world!
We have a relatively small development team and need to grow to meet demands. We are seeking full stack DevOp engineers to work on a variety of projects such as replacing legacy backend systems, develop new client features, and expand our DCA technology.
Some of the things you'll play with:
• Node.js, C++11, and a bit of native Android (Java) and iOS (Swift) code
• AWS, large amounts of data, and hundreds of thousands of clients
• Nitty gritty system level programming all the way up to UX
• Work with a small team where YOU can make a difference
We prefer onsite but are open to remote given the right candidate.
Contact bashby(at)contentwatch.com
Keywords: REMOTE