Then I see that I can self host it. This is interesting novelty.

But there were so many bad apples in CAD area, that I will stick with FreeCAD and after 20 years, if this will evolve and prove it is just not another scam, happily give it a try.

All my love <3 <3 <3 to organizers, thank you for continuing the IOCCC context, please never go away again!

Comments URL: https://news.ycombinator.com/item?id=48219446

Points: 2

# Comments: 1

Meanwhile some things just dont let me sleep... it was more fun while decompiling games and trying to understand a logic in good ol' times...

(function() { let itbe = 99999; let rawSave = localStorage.getItem('gacha'); let decoded = atob(rawSave); let saveData = JSON.parse(decoded); saveData.clubs = itbe; saveData.spades = itbe; saveData.hearts = itbe; saveData.diamonds = itbe; let reEncoded = btoa(JSON.stringify(saveData)); localStorage.setItem('gacha', reEncoded); location.reload(); })();

Opened everything possible, I still have 3 locks to open, battle at 2001 (level 6), the attacker movement is just too fast to be able to react.

Would be probably doable by keyboard but with mouse I just closed the browser tab as with 3 more locks to go, it just doesnt make any sense to even try.

They have lost 3785.90 euros in sales due to their idiotic anti-user war.

Not to mention of all bad reputation that I gave them.

Or anything to defend on Meta. If they go out of business, humanity profits.

I have ONE static external IPv4 for my network.

I can handle everything I want with it. And block everything I dont want my network to be.

So I just disable IPv6 on router (Mikrotik).

Not interested, not wanting it. That is it. If someone needs it, feel free to use it. I wont support double configurations on my router because of it.

Once Jolla will understand that, I am prepared to get back. Until they don't, they will need to find users elsewhere. I can ditch a lot of bloat from my life, but unfortunately, ability to use public transport is not one of them.

Believe me, I am in front row, for wanting the linux to succeed against bastardized OS as android is. But the wrong decisions are just wrong decisions, there is no excuse to it.

I cant emphasize enought how this feature is of most importance for my daily life. At 48, I am using either the bicycle or public transport for my daily commute (for 30+ years!). I can workaround it by buying a NFC card each month but very typically it is not available without considerate walk time. Not to mention banking app, but I have covered it by reversing and patching it. How many users will do that?

It is not my fault, that the world is as it is. But not supporting real life scenarios is certainly Jollas fault.

I have struggled for 2 years. Most users wont.

TLDR: while the OS is great (really GREAT), the real-world compatibility is not.

I had Sailfish OS for a daily driver for two years, and OS is great (let me say that again, Sailfish IS GREAT!), but there are "the details".

Jolla is completely ignorant to needs of their users. While they do have an android layer, they are ignoring to things that are of huge importance for daily life, like bluetooth passtrough, and are important due to daily needs, for instance, bluetooth passtrough is really important for using public transport here.

FFS, I was reversing banking application and patching it to be able to use it. And actually became very good at it :D

Here is a bluetooth feature request thread, that is open for 5 years: https://forum.sailfishos.org/t/bluetooth-support-in-android and being blatantly ignored.

And lets not get into details, like NFC.

So at the end you will have a great OS, incompatible with the whole world. After 2 years of suffering, I ditched Sailfish, bought Pixel and installed Graphene OS.

Once Jolla starts to listen to their customers, they are on the path to very real android contender, but unfortunately they just dont understand, that people need some features, they are not providing while the vendors wont support some exotic OS. They need to adapt, not vendors - the whole thread is full of this mentality.

The android "container" was a step into right direction but they just shouldnt abandone it and keep on supporting it, adding additional layers of compatibility.

I really hope they will change their mind at some point and prioritize compatibility, would love to ditch android and its spyware driven ecosystem completely, but sadly, Graphene OS + NetGuard is just a far better alternative until Jolla stops behaving like an infant. They are literally sabotaging themself in a worse possible way.

I just dislike the scripted languages as they are a mess to handle while docker is a resource waste, not to mention golang single statically compiled binary and speed of execution.

Authors, please think really well about:

- upgrade strategies (owncloud/nextcloud were a huge mess, for long time, currently looks that nextcloud is handling it well - I have upgraded it for 2 versions and it didnt break anything)

- what external dependencies you are using, make additional layer of OS abstraction to avoid incompatibilities between various linux distributions, freebsd and windows. There isn't a lot to handle differently but once you tie yourself to linux only, it is hard to add support afterwards (try to not call external binaries that you havent installed yourself, if you must, put it into compatibility layer). If you do this one right, people will port it to different environments, if you blow it, you will have to - or you wont.

- do not rely on docker "installation", presume that it is installed directly on the system and you wont go far wrong. Treat docker just as another system. Docker is going to make you become "lazy" to not think about vital details while developing.

- do check how to handle reverse proxies gracefully, this is something everyone forgets while for any serious environment, there will be nginx frontend

- dont support all the databases, pick one and stick to it, to support it really well, including backups, upgrades and versions - sooner or later redis is going to be a must, think upfront

- make a backup system, backup before upgrades and be sure you can restore it if something goes wrong, including binaries, database,...

- make an installation/upgrade layer that doesn't depend on "run this sql script", have a well versioned database revision system that can get database from version "0.1" to "2.0" without breaking anything and migrate the data. There are hardly any database changes where database upgrade cant be handled with sql statements.

- think really well about external dependencies, dont pick it just as it is popular and you need one functionality. An example, recently I did a benchmark of 15 concurrent maps in go and the differences were huge where the fastest one was one that you can hardly find by searching while the author did things like aligning the structures with cpu cache, full of unsafe pointers etc., but beating the first selected "popular" map by 2x, and the worse by 15x+. Dont trust authors self promotion, measure it.

- try to not make it confusingly strange, you have the whole usage/administration well done with nextcloud, stick to it, dont reinvent what works, as for instance, sftpgo did and I hate every second using it.

- if something needs to be documented, think about how to implement it, in a way, that doesnt need to be documented. Over time those documented features become a huge burden for you and for users.

- please, if you dethrone nextcloud, dont become evil, like projects normally do. Get the money from where the money is (smb, corporations), spare the home users. :)

Good luck!

(I would love to explain more, but deliberately type of error and company name were omitted, anyway it is fixed for a decade)