Hacker Newsnew | past | comments | ask | show | jobs | submit | synchronise's commentslogin

How do these go with OS support? Not much in the way of reviews on Youtube but I've seen a few where the driver support leaves a bit to be desired.


Mostly okay, the OSes are really getting there. Most of them are shared with that of the PinePhones.

The driver support is also mostly there. I believe for the PinePhones pretty much the entire hardware is working and usable. They are still not daily drivers, but it gets closer each day.


They have something similar in Aus called the Capital Gains Tax and it is something that is inherrently political, unfortunately you can't uncouple the government from as they provide the public service that maintain and collect taxes. Honestly the public service should be answerable to parliament, not government.

Not to mention CGT been tweaked to ineffectiveness by previous governments by excluding assets from its calculations, notably housing, which has skewed CGT away from its original purpose and it's now more of a stick to whack at industries that aren't cozy with the current government.


The US has a CGT, capital gains are taxed at your normal marginal income tax rate unless you hold them for a minimum time in which case you pay a slightly lower rate. Though they do provide some exemptions for the family home. Not all that political thing.

In fact in many countries CGT is only used to refer to the LOWER version of the tax ... after all you should pay income tax whether you make your income digging ditches, house flipping, or day trading


Someone is working on a LineageOS-like project for KaiOS called GerdaOS, and there's code for the Jiophone 2 in the branch.

Not sure if it compiles yet for that particular phone but here's the repo if you're interested: https://gitlab.com/project-pris/system


FirefoxOS was also exclusively targeting the touchscreen market, which by that point was already totally saturated. Their partner deals weren't the best either, and they really launched their product before it was ready which sullied their image quite a bit.

KaiOS had the benefit of hindsight to see where Mozilla fell over, put in mitigations, and then shift focus to non-touchscreen devices to lower costs even further.

A lot of their stack is still open source under the MPLv2, however there are rumours that Google is 'encouraging' KaiOS to shift their rendering engine over to Blink. Whether this happens or not remains to be seen.


Mozilla started a feature phone project, that was later canceled. One issue at the time was that the carrier partner was Verizon, and that was a huge gap of values due to how VZ was fighting against Net Neutrality.


Switching to Blink would be a huge undertaking, ditto for moving off classic Gecko.

Mozilla ditched Firefox OS & Thunderbird over the huge amount of work that would need to be redone to move to newer Gecko (as Servo components were ported over and swapped in via Project Quantum), but that would likely be less work than getting Blink to be responsive with minuscule amounts of RAM, then go app by app and optimize the crap out of it (which Mozilla had dozens to hundreds of devs doing for Firefox OS while they were developing it).


Actually, there's not been much change from the original fork of FirefoxOS besides the UI changes to be better for non-touch devices.

GerdaOS (LineageOS for KaiOS) allows people to import and run FirefoxOS packages without modification, though many apps will need some changes to allow it to work without a touchscreen.

The unofficial rumour mill says that with the extra investment from Google, KaiOS will probably shift to Chrome(ium) at some point in the future, but that's just a rumour and remains to be seen.


I doubt KaiOS would switch to Chromium, the focus seems to be using near zero resources while remaining somewhat fast.

Mozilla spent years with dozens to hundreds of devs working on getting it to be snappier than every other low end phone, short of Google paying for this type of dev work on KaiOS, there will likely be nothing more than security patches and cosmetic changes to KaiOS.


Just had a look over Harvey OS, looks like a pretty neat direction to take Plan 9.

But it got me wondering, is there any shared collaberation between any of the next-gen 'Plan 9-like' OS's like 9atom, 9front and Harvey OS?

Also, it looks as though Harvey OS is only using Slack for its discussion forum, which is a bit odd for an open source project.


9front views HarveyOS with scorn and I don't think 9atom is developed.


why is that? got any references?


HarveyOS is "plan 9 with gcc" but 9front doesn't like gnu stuff. See cat-v, suckless, and their IRC channel.


ah, yes, i can see the problem.


So, this is essentially a continuation of the Natami project, but you still need original hardware?


This is the Natami, and yes, real hardware is needed.


... for now.

Vampire v4 should have a standalone version.


Mastodon is a decentralised Twitter, Hubzilla would be the decentralised Facebook.


Has the code always been licensed CC-BY-NC-SA or is that a recent change?


It wasn't at first. The change happened over a year ago.


Under Australian law public domain exists but only after the full copyright term expires. There's no legal mechanism for an author to relinquish their copyright over their works and dedicate it directly to the public domain.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: