https://web.archive.org/web/20040902191610/http://www.c64hq....
512 karma · joined November 24, 2021
https://web.archive.org/web/20040902191610/http://www.c64hq....
[1] https://en.wikipedia.org/wiki/EMX_(programming_environment)
[1] In Italian: https://it.wikipedia.org/wiki/Storia_del_debito_pubblico_ita... [2] https://www.economist.com/special-report/2022/12/05/why-is-i...
And software in those countries always has the "English name" field.
So I got used to using US keyboards also, and never using accented letters even though they are frequently used in Italian, e.g. instead of writing "Mario è alto" (Mario is tall) I would write "Mario e' alto". It helped a lot that I worked for almost two decades for companies having only non Italian clients and all communications internal and external were in English.
Now that I am working for an Italian company with Italian clients, I am slowly getting used to Italian keyboards and accented letters.
The lawyer even insisted that the hyphen had to be clearly visible in the signature. I think that in those types of documents in Italy you are legally required to use a readable signature, because I bought/sold house a number of times as family grew, and every time different lawyers always insisted on this aspect.
The codepage was very specific, it was not part of the standard Java JDK but it was included in the IBM Java JDK.
Even better, when I was a kid and I got my first official document, the national healthcare card, the software in use did not allow a space character in the first name. The operator then decided to add a hyphen to enter the two parts of my name as separate words.
Fast forward many years, and I my first name shows up with the hyphen on the ID card and healthcare card, while it does not contain the hyphen on the driving license, which of course I got much later when software had improved.
Generally this is a non issue, nobody ever said that it's not me because there is a hyphen or a space in my name, however when I signed the mortgage for my house, the layer asked me to sign with the hyphen, and in the document he wrote both variants of my name with an A.K.A. clause.
Because of that, my grand father and his sister happened to have different family name in their ID cards: when they got registered by the priest at the beginning of 1900, on a paper book of course, the priest who registered the sister added an "I" at the end of the family name as he thought that that should be the right spelling in proper Italian. At that time ID cards did not even exist so nobody bothered.
There was a lot of uncertainty about the future of MySQL... The original authors forked MariaDB and MySQL for many months did not receive any update.
When I find something interesting on github, before deciding to use it, I check the number of committers and the commit history/frequency.
Anyone can do the same for Apache projects.
There are still a lot of projects at Apache.
Check their last annual report [1], especially the sponsors and the statistics sections.
[1] https://apache.org/foundation/docs/FY2023AnnualReport.pdf
I believe that the death blow which lead to the fork LibreOffice was the lack of trust in Oracle commitment to Open Office and open source in general, after Oracle acquired Sun Microsystems.
Sun indeed had largely reduced its involvement in the project in the last years, and there was the "Symphony incident" [1]. The death blow was when Oracle arrived, started the trial with Google over Java/Android, inherited MySQL and almost killed it, inherited OpenOffice and the future did not look bright anymore [2, in German]
[1] https://web.archive.org/web/20130927072255/https://lwn.net/A...
[2] https://web.archive.org/web/20131024094250/http://www.heise....
At that time in Italy we did not have free local phone calls, every call would be billed based on its duration.
Now imagine being a Fidonet sysop who on a volunteer basis was running a computer at home 24/7, often having a second phone line dedicated to the computer (at the time even more expensive) to make sure that your users would not clog your home landline making you unreachable all day. Plus overnight your system would need to dial up and connect to your hub and exchange all data produced by your user's discussions (echomail). All the costs were on the sysop and the national hubs in Italy would then exchange with a system running in Belgium or the Netherlands, system which would in turn then exchange with USA. Flat rates did not exist (at least in Italy), and no sysop was asking (at least in Italy) end users to contribute with money or a subscription.
That is why content was moderated in the first place, to avoid off topic discussions that would waste byte and increase the bills. For this reason you would also need to limit signatures, tag-lines and so forth to 80 bytes, which IMHO are more than enough for a signature, unless you want to add ASCII ART to it.
And it sounds totally legit to me. If instead what you are referring to is something similar to Electron, that is something I "hate"; I understand it's a cheap way for a Web Developer to reuse the skills and build a desktop application, but the result is typically buggy, bloated, slow, and does not integrate properly with the desktop environment (fonts, colors, clipboard, accessibility are just the first things that come mind).
Did you ever tried implementing a desktop UI using an object-oriented multi-platform toolkit like SWT or QT or GTK? There are good chances that all the dependencies you will need are already "there", you learn the widget toolkit bindings for your preferred programming language and you can start. It's so much more productive and fun (at least for me) and most of the time you don't need to mess up with colors, styles etc. etc. because you will want the operating system to take care of that.
On the Web you have so much more freedom, because the web page is almost a canvas, but at the same time (for me at least) it looks way less productive and everytime I think of it, I always wonder why nobody is proposing anything better for the Web and the industry keeps on building layers of complexity on top of JavaScript/DOM/CSS.
As such you could fork it, tweak the code around the license verification to always return TRUE or whatever, and you would be running a "pro version" of the software.
The developer simply trusts that people who like the software will purchase a license, or the fact that the majority of people out there are not programmers and would not be able to rebuild the software for themselves. Besides, the product is also offered as a SaaS.