Floorp – A customisable Firefox fork from Japan
floorp.app
floorp.app
Another is this phrase particularly signals to other Japanese: Hey, choose this software, because it was made by our kind (pride), and its operation might mesh better with your cognitive patterns. oh, and the Japanese localization is bound to be 1st class (a small rarity).
One more: Japanese like to judge things after getting the thing into their hands and evaluating it (物で判断する), and word-of-mouth is mighty powerful in Japan. So "built in Japan" means it's pre-vetted by Japanese, and that is in turn a powerful seal of quality. Oh, and if there are some flaws, we can overlook them knowing that someone will eventually get round to dealing with them. It's a civil and respectful community-minded approach that mirrors Japanese culture in the large.
If you are so inclined, there is a whole multi-faceted Made in Japan movement.
Outside of the context of Japan or being of a Japanese mind, the value of this statement depends greatly on the context. For medicine, semiconductors, industrial equipment? Made in Japan is often a solid choice. For software? Japan is an advanced nation, plenty of highly-skilled knowledge workers, and has a very long history with software development; this software is probably competently done. On the other hand, it might mean the software is designed a little .. mysterious .. to non-Japanese eyes due to those aforementioned cognitive patterns but also a differing cultural context. For example using the color blue to signify "build successful" in Jenkins instead of green.
I think countries mostly fall into one of two baskets:
* those who normally favor their own country's products.
* those who almost universally loathe their own country's products.
I was born in one of the latter types of countries. Where I am from, the word "imported" was absolutely synonym with "better quality". It didn't even matter where it came from, as long as it was not local. This was due to 1970's and 80's protectionist/socialist policies which wanted to make the national industry protected from foreign competition - which it did, but had the side effect of making such industries completely non-competitive with the rest of the world.
Then I moved to a country in the more nationalist group: Australia. The "Australian Made"[1] logo is proudly used by anyone who produces even a tiny bit of their products in Australia (I think there's a minimal threshold for that to be allowed, but didn't really check it)! The most popular car there was the Holden Commodore for decades (recently, Holden closed down production in Australia - so now it's all Toyota), proudly Australian made - even if the mother company, GM, was not Aussie. After traveling around in a few countries, I came to the conclusion that most countries that actually have a competitive industry tend to be more like that. Japan is of course in that category, but so are most developed nations: USA, Canada, Sweden, Germany, Italy, even more recent "arrivals" to the upper league, like South Korea.
Poorer countries tend to be in a paradoxical position where their people will swear they love their nation and will be extremely irritated if any foreigner dares to criticize them, but in private they consider their own industry a joke, will go to great lengths to buy "imported" products, even if they're more expensive (given the high tariffs for imports), have almost zero trust in their compatriots (specially politicians and business people) and totally expect them to be dishonest without further evidence to the contrary, and so on... things that just lead to a self-fulfilling prophecy.
Anyway, I just wanted to say that this is not at all particular to Japanese people :).
the isolation policy in the past didn't come from nothing.
everywhere else it generally also differs by industry more than in japan.
In Indian rural side, "desi" (native) is almost always synonyms with bad quality, not cheap which is implied, but bad quality. I heard that desi in many foreign country means Indian?!
Desi or swadesi (home made) had a special emotional appeal to urban upper middle class leadership during freedom struggle. I don't know how they feel about it.
Chandrayaan from ISRO was a very significant moment in this regard. Done by desi engineers educated in desi schools. I am one of those.
(As an aside, it's rather difficult to accurately describe my ethno-national status given the regular confusion with people of the First Nations...)
Heck, most of us are effectively different people than we were in the past. And we very much feel some shame when we find out something bad we did back when.
Do you feel shame when you read about someone stealing a bike in a far country whose capital you wouldn’t know ? You must be in despair over all the crimes committed by humanity every hour
Do I also think it is arbitrary? Yeah. But I am also ok not feeling shame at stupid crap my immediate family has done. I just have no surprise that others do.
My guess is you are taking a narrower view of this than you intend? People don't necessarily take personal pride in what others have done. But identity is both personal and societal. And any accomplishment of identity is something that people are likely to feel pride in.
That is, pride is often tied to identity. And identity has a pretty wide brush.
On my phone I just added Japanese as a language and it now prefers those. Windows seems to support it fine too, as does Chrome on Linux.
I guess there are problems if you try to use two languages in the same application.
Is the text you're reading getting rendered in Japanese characters? Or is it getting written in similar-but-not-quite-the-same (and thus something you can use, but irritating to do so) Chinese characters?
Then again, it is a difficult taks. For example, there are three ways to write the first (topmost) stroke of 言: as a slanted dot (now PRC standard), as a short vertical (very common in pre-war prints, still used in Japan) or as a short horizontal (also very common). Sure, one can make three codepoints out of these, no big deal. But then 言 occurs in a gazillion of other characters, as in 說這語信 and so on; all of these characters would then need to get codepoints of their own (which btw is exactly what happened with 說 vs 説 (and incidentally 说)). It gets worse when you consider that another one or two components of a given character may also have two or three variants, then you might get 3x2=6 or 3x2x3=18 codepoints for what most people consider a single character. And did I mention we already have around 100'000 codepoints for CJK Ideographs? That number would multiply considerably.
Although I've worked extensively on these problems—what is a variant, what deserves a codepoint—all I've found that there can and should be guidelines, but there's no very hard and fast rule. And I'm afraid variant selectors are a cop-out, not a solution.
In practice in the pre-unicode world fonts were encoding-specific, so the encoding did help. When you viewed a Japanese document it would be in a Japanese encoding and you'd get a Japanese font, when you viewed a Chinese document it would be in a Chinese encoding and you'd get a Chinese font, and when you mixed up your encodings you'd get something that was obviously broken even to someone doesn't speak Chinese or Japanese.
> but those apply across all concerned languages and are not unique to Japanese
They're de facto unique to Japanese; Chinese support "won" in most international contexts, so "CJK" codepoints look fine in Chinese, and those codepoints are rarely used in Korean (mainly in historical documents) so having them rendered "wrong" there matters less in everyday life. Admittedly looking at another article that hit HN today I could believe Bulgaria gets equally shafted (and is probably, sadly, less capable of sustaining a "made in Bulgaria" software ecosystem than Japan is).
> Sure, one can make three codepoints out of these, no big deal. But then 言 occurs in a gazillion of other characters, as in 說這語信 and so on; all of these characters would then need to get codepoints of their own (which btw is exactly what happened with 說 vs 説 (and incidentally 说)). It gets worse when you consider that another one or two components of a given character may also have two or three variants, then you might get 3x2=6 or 3x2x3=18 codepoints for what most people consider a single character. And did I mention we already have around 100'000 codepoints for CJK Ideographs? That number would multiply considerably.
You don't have to add 18 variants, only 3, and that's the worst case. We don't need codepoints for letters that are half-Japanese half-Korean, or every other conceivable variant. But using Unicode shouldn't be a regression from using Shift-JIS.
Nobody wants to go back to a world with hundreds of relevant and thousands of legacy encodings.
> when you mixed up your encodings you'd get something that was obviously broken even to someone doesn't speak Chinese or Japanese.
Obviously much better when nobody can read anything than forcing some people to read texts where there's the occasional odd ('non-native' if you exaggerate a bit) font style choice.
> We don't need codepoints for letters that are half-Japanese half-Korean, or every other conceivable variant
Things are more complicated than that, I'm afraid. For one thing there's time, so setting the language in your HTML document or element to Japanese will give what is considered correct in Japanese today, not what was considered correct pre-war or any one time before that. There's no formal way to express that. Second, stylistic choices on one and language + region selector on the other are cross-cutting concerns.
I have to say that I find your criticism not very well founded. What you can do today is (taking HTML+CSS as the obvious choice) is proper font choice, `@font-face` declarations, proper downloadable fonts, proper configuration of OpenType font feature flags, if necessary on the basis of Unicode code point ranges. (There's also Unicode variation selectors, bit I've never worked with those so can't say how well those work.) This will get you a long, long way to achieving correct and typographically pleasing output for any text be it Chinese traditional or simplified, Japanese, or Korean. It is some work, but then it is a vexing and somewhat convoluted problem, too. I think one should give font designers more credit here because good CJK fonts typically go to great lengths to satisfy even the finickier type heads among us, enabling variations that I'd frankly just gloss over for heavens sake.
It's not like the pre-Unicode chaos of mutually incompatible encodings did anything to help you with any of these points. Rather, it locked you into a rather small (when compared to Unicode) set of codepoints, and you typically only could do one setting per document. So, no writing about Cuneiform or Hieroglyphs in Japanese. Today we can intermingle LTR and RTL scripts, and you can freely mix hundreds of scripts in a single document and a single encoding. None of that was possible in the good old days.
Japan does (assuming agreeing a unicode-like encoding that actually worked is off the table), for the simple reason that practical support for Japanese in "international" applications has regressed since those days.
> Obviously much better when nobody can read anything than forcing some people to read texts where there's the occasional odd ('non-native' if you exaggerate a bit) font style choice.
https://wiki.c2.com/?AlmostCorrect . Failing obviously and universally is better than failing subtly in edge cases.
> What you can do today is (taking HTML+CSS as the obvious choice) is proper font choice, `@font-face` declarations, proper downloadable fonts, proper configuration of OpenType font feature flags, if necessary on the basis of Unicode code point ranges. (There's also Unicode variation selectors, bit I've never worked with those so can't say how well those work.)
You can do a lot in HTML because HTML has a lot of specific support - something that would likely also be true in a world without unicode. (In the unicode world we have only one encoding per HTML file, but there's no reason a file format couldn't support multiple encodings in the same way as supporting multiple language spans etc.).
> It's not like the pre-Unicode chaos of mutually incompatible encodings did anything to help you with any of these points. Rather, it locked you into a rather small (when compared to Unicode) set of codepoints, and you typically only could do one setting per document.
The old system made the easy things easy. In those days effectively any program that could display French or Swedish documents could also display Japanese documents.
The unicode world makes some things that were previously hard easier, such as mixing languages (as long as the lanugages you want to mix aren't Japanese), but your file format has to go beyond "plain" text for the most basic functionality of properly displaying monolingual Japanese documents.
In the old days if you didn't think about languages at all your program would be broken in every non-English language. Now it's broken only in Japan. That's an improvement for most places, but it's a huge regression in Japan, because previously most programs made some effort to deal with internationalisation issues and now they don't, they just say "it's unicode so we don't have to think about it".
So you write, You can do a lot in HTML because HTML has a lot of specific support - something that would likely also be true in a world without unicode. (In the unicode world we have only one encoding per HTML file, but there's no reason a file format couldn't support multiple encodings in the same way as supporting multiple language spans etc.). Basically you reject a format—HTML+Unicode—that has seen tremendous global acceptance, that has brought us 'rich text' (to quote Microsoft), near-complete universal language support for hundreds of previously entirely unencoded writing systems, ability to display ruby text (i.e. small annotations, parallel version of text; btw. not limited to Japanese at all) and want to replace that with 'a file format [that] support[s] multiple encodings'. I agree that it would sometimes be nice (i.e. nice-to-have) inline encoding switches in HTML. You could totally write a JS method to do exactly that, right now, so go ahead! But to replace HTML+Unicode with 'some unspecified file formats' that 'could have' multiple encodings in a single file? Doesn't sound like I want to go down that particular cul de sac.
OK now on to that other point: you write your file format has to go beyond "plain" text for the most basic functionality of properly displaying [some features for some linguistic situations], if I may be so bold and generalize to avoid that fixation on "boo it's Japanese again and only Japanese that has been put at a disadvantage". So where I agree with you is that historically the Unicode consortium was too reluctant to acknowledge responsibility for some features of written text that should be expressible in the very text, not in a 'side channel' (e.g. in HTML tags). This would IMO include markers for start and end of stretches of a language, so you could write "good day, {lang=fr}Messieur{/lang}" where the curlies symbolize where Unicode control character sequences (not unlike those already used for flags) should appear. There's more stuff like that like e.g. indicating position of text relative to other text; we sort of have it in the form of CJK Ideographic Description Characters and Control Character for Ancient Egyptian, but nothing for the general purpose.
It's not rosy glasses lol, I have to deal with encoding differences every day. I'd like nothing more than to be able to forget about them if there was something like unicode that actually worked. Instead I watch support for the language I'm using degrade day by day because everyone high-fives each other that they've got unicode now so they've solved all the problems (and they have! As long as you're not using Japanese), and then they add insult to injury by trying to tell me it's better.
Sure when you have unlimited time and unlimited resources why accept anything that is even a hair's width not quite like what you intended—perfection?
Meanwhile we have Unicode with all its flaws. Sick!
I wonder why they couldn't have done a composition system like Hangeul?
We don't live in a world where any part of this holds water, at least I don't. Care to elucidate where exactly HK and Taiwan got their full set but Japan didn't?
> I wonder why they couldn't have done a composition system like Hangeul?
The answer to that question is because it's too difficult. I worked a bit about automatic CJK character generation ion the early nineties, around the time Unicode v1 and then v2 came out. Nothing at the time resembled anything anywhere close to aesthetically pleasing output. Quite a number of people tried over decades, not a single paper demonstrates acceptable character shapes, only 'legible' and 'bearable' ones at most. Given recent advancements in AI text-to-image, it wouldn't surprise me if someone has already tried their hand at providing a model for CJK generation. But even then you'll be computationally much cheaper to just generate images for given code points plus those few unencoded characters that have to be generated ad-hoc.
Characters from "Traditional Chinese" and "Simplified Chinese" have different codepoints even for "the same" character, whereas characters from Japanese (or old Korean) are made to share Chinese characters' codepoints even for visually different characters.
You'll find all the gory details of what changed between JIS encoding editions in this fine book: 大熊肇: 文字の骨組[1], esp. pp164—178 where all the fine details between different editions of the JIS encoding are listed. It's mind-boggling! It's almost as though the Japanese standards body itself has been having slightly different opinions about their own writing system over the decades. Now if you're intent on getting all the fine details just right for your print edition you can either apply a newer or older JIS encoding to your document, OR invent that file format you're talking about where you can switch encodings mid-way, OR access OpenType font features from your document somehow... mmmh... how to do that... mmmh...
Oh I know! Let's use Unicode and HTML and CSS and get full access to OpenType font features for any point in the document on a per-codepoint basis.
For those folks who really pine for the bad old days when all we had was US ASCII plus an insane number of other encodings, please do read this single Wikipedia article: https://en.wikipedia.org/wiki/ISO/IEC_2022 it will change your mind.
* [1] https://www.amazon.co.jp/%E6%96%87%E5%AD%97%E3%81%AE%E9%AA%A...
No it doesn't. Unicode has no problem with including multiple codepoints for characters that are (arguably) not visually distinct, and has already done so, many times over, not least for simplified vs traditional Chinese (but also for e.g. Cyrillic vs Latin). Just... not for Japanese.
> It's almost as though the Japanese standards body itself has been having slightly different opinions about their own writing system over the decades.
Slightly different, sure. Doesn't mean "just write it all in Chinese" is acceptable. I'm not asking for pixel-perfect everything, just for the ability to write the native everyday language of over 100 million people without having to use some half-assed out-of-band font setup that always has some funny edge case where it breaks.
Shift-JIS or whatever 0x5c shenanigans were immediately brought back to mind.
https://web.archive.org/web/20061208222907/http://blogs.msdn...
Still makes ripples to this day:
https://superuser.com/questions/1167662/why-is-windows-10-di...
It makes it hard to use Unicode for historical documents with older variants, documents using more than one CJK language (like talking about Chinese in Japanese), and worst of all, a lot of theoretically-compatible CJK fonts look wrong because they chose Chinese glyphs.
There's many ways Unicode is an improvement over what came before, but they screwed up with Han unification.
Just like I've seen in Linux for 20+ years, we see different tribes basically working on the same thing in slightly different ways, and I find my self thinking over and over "Why are all these people building different sandcastles when they could be working together?". Particularly with the Firefox forks where projects seem to struggle with the release cadence.
It's a rhetorical question though - effective organization appears hard to scale especially when there is no money involved. How many cash rich companies have you worked at that have lost the plot?
I would really like to see Firefox win again in the browser battles. I personally believe that its the UX where differentiation from the chromiums is opportune with many interesting and desirable new UI paradigms emerging in some the recent third-party browser upstarts.
So, many times you don't do it as a way to kill time. You do it because none of what you have works.
If I had time and enough knowledge of any of the existing browsers codebases, I'd definitely try to create my own version. Here are things that are desperately needed and some even have been removed from browsers for no reason that I would like to have back.
1. Keyboard-driven interface.
2. Decent access to the browser's internal state for testing purposes.
When it comes to (1), there used to be a common pattern where pressing Alt would underscore letters in labels necessary to press in order to select that element. This is long gone now (and, frankly, wasn't that great, but it was something...) To clarify: it's not gone because the feature was removed, it's gone because a lot of controls simply don't have any labels, which breaks the system. Today, most browser elements have no way of activating them with the keyboard. Just a big middle finger from browser vendors.
When it comes to (2), the only thing we have is Selenium (and sometimes some extra stuff on top of that). But, Selenium has no access to anything that happens in the networking side of things (that's in the Web browser, which is all about networking... right?) So you cannot know if the page is loading anything, what it's loading, what's the status of things being loaded. It's ridiculous that people write tests with this handicap. With Selenium you also don't have access to code execution. So, you cannot see if the function was called, a variable was set etc. It's ridiculous how poor your access to the state of the program running in the browser is.
You used to be able to side-load some JavaScript into the browser and get access to browser's chrome, but that was removed because it was a "security concern" (but really, power-user features being removed is just a plan for cutting down functionality that affects the least users, has nothing to do with security).
Do I expect Firefox or any other browser to implement any of that any time soon or ever? -- Well, let's limit that to my lifetime, and the answer is a resounding "no". Hence forking.
Could they, though? What if upstream says ”thanks, but no thanks“ to your ideas? What if there are multiple, equally valid solutions to a problem, and you want to explore one that wasn‘t chosen?
Progress isn‘t linear, and not everything can be compromised on.
Just having more people work on a project, does not magically speed up development. You need leadership, a common goal, consensus, and focus.
If all these projects merged their efforts, that would probably result in a lot of lengthy discussions and infighting, rather than improvements.
I agree with you, growing beyond a single small team is another game entirely
Why are chefs baking bread? There's buildings to construct.
- Most of Floorp's features are native, so unlike addons they won't slow down Floorp by much
- Vertical Tab being native makes it faster than anything else
- Sidebar is useful for multi-tasking
- Sleeping Tab saves system resource, and it's light for an tab unloader
- Workspace is like Panorama, very useful to create multiple work environments, and plus you can wrap them in containers to get the most out of Firefox's container feature
- Customizable hotkey is useful to rebind your hotkey, improve keyboard browsing experience, one of the rare browser that support hotkey rebinding.
(bottom tabs - seems previously it was possible to do that for vanilla Firefox via userChrome.css but that becoming harder to do which each release)
Waterfox has had these features for a few years now.
Why you need tracking protection. Try javascript fingerprinting:
The end result gives a much cleaner interface where I can focus on page content and not surrounding UI. The built in mouse gesture plugin (which can be added to Firefox) takes me back to early Opera. I forgot how much I enjoyed using them.
I don't understand caring at all about the source, unless there is some fundamental moral hangup with it (such as blood diamonds, for instance).
Generally European countries provide the best protections and the fact it is published in Japan may imply that the US laws don’t apply there (and be a + or not)
Other people care about work conditions for the produced items they buy, namely not manufactured by children, for which country origin could be an indicator.
Which is pretty dumb thing to care about, since these journeys have minimal carbon footprint, compared to something like local delivery
Cars made in foo are good, tv made is bar have bad QA
It was very true before, but more like 10 years ago.
For example, Apple, one main reason they chose to produce a lot of the phone in China was because of infrastructure and skills that people have, and not costs anymore.
China (in particular when you see markets like Yiwu!) has an impressive ability to produce all type of quality and grade of products.
China has some of the best factories, supply chains, and collaboration in the world. And while yes, of course, loads of intentionally cheap, low-quality goods are churned out regularly, many Chinese companies also make really solid products, often even the best products until you reach a certain ultra-luxury price bracket that they simply aren't trying to compete in.
For example, sure, an LG/Samsung/Sony OLED will be way nicer in terms of picture quality than any Hisense on the market. But the cheapest OLED on BestBuy right now is a last-gen, clearance 46" LG that costs almost ~$700; if you want a 50"+ model, be prepared to spend $1,000 minimum. On the other hand, the 75" U6H I got for $600 was better than any comparable non-OLED offering by non-Chinese companies until you got into the $1,000-1,200+ price range.
Midea is another good example; sure, Bosch, Miele, and Zojirushi often have much nicer luxury products, but if you're a middle/working-class person who doesn't want to or can't spend $300+ on a rice cooker, it'll be hard to beat--unless you get lucky like me and find the one weird guy in your town who happened to be moving cities and selling off all his appliances, including some perfect-condition JDM Zojirushi with an inverter for $100 (and also happen to have a Japanese friend you can annoy to help you figure out what all the Kanji menus do).
Same can be said for handset manufacturers like Xiaomi, etc. And a lot of audio gear as well; $100-200 Russian Oktava microphones easily punch several hundred to several thousand dollars above their class, Chinese brands dominate the mid-range IEM market, and Chinese headphone brands like HiFiMan are difficult to beat in any price bracket -- first paycheck I got, I spent $1,600 on Sennheiser HD 800 S because I wanted the HD 800 as a kid, but realistically, $300 HiFiMan Sundaras will get you almost there for over a thousand less.
Personally, every "made in America" thing I've bought that wasn't manufactured before like 1990 either fell apart and/or was ridiculously expensive compared to things made elsewhere. My association of made in America is either:
A. Truly craftsman, low-volume, specialized products that have an inherently high price tag
B. More commonly, low-quality, over-priced junk that survives only because of nationalism or protectionism alone
> China has some of the best factories, supply chains, and collaboration in the world. And while yes, of course, loads of intentionally cheap, low-quality goods are churned out regularly, many Chinese companies also make really solid products, often even the best products until you reach a certain ultra-luxury price bracket that they simply aren't trying to compete in.
Rather like conservatives' reflexive dislike for California despite more registered Republicans living in California than any other state.
https://worldpopulationreview.com/state-rankings/registered-...
I am from neither country, from the perspective of residence, origin, or that of my family. I have absolutely no horse in the race. I just can’t believe that in 2023 Americans still believe this. Does anyone else remember Mac Pros being built in the US 10 years ago?
With these kinds of things it's basically, I have no way to differentiate my product, so I'm gonna slap the country flag on it for good measure
In many parts of France, simply displaying the French flag in front of your house is very dangerous, whereas it is perfectly normal for everywhere else.
Most successful French startups move their HQ to US as soon as they can and claim they're a US company.
"Made in France" software is a shame and if you're targetting the global market (not just the French domestic market) no founder wants to advertise that.
Which is a shame because we have a lot of talented engineers in France, it's just that the biggest French software companies are frauds.
I'm pretty sure it is more a question of astonishing level of taxation and the difficulty to rise capital than national pride.
> "Made in France" software is a shame
Any source to back this? I've never read or heard anywhere that a piece of software sucks because it was made in France. I'm pretty sure most people don't care, and those who do (Frenchmen) take it positively.
There are, however, perceptions among the Japanese people that their own products are generally off higher quality.
> If you download Floorp you agree to the <h1>Pricacy Policy</h1>.
If you are US company you don’t have a choice as it is the law.
Mozilla, Google, Facebook, Cloudflare, Signal, all have to respect the local laws.
Stop over thinking and just appreciate people work.
And meanwhile, Japan has been the biggest video games actor in the industry for the latest 50 years, so I guess there are some engineers over there.
If you have experience in the video game industry, then I think you get my point but I also enjoy arguing about metrics.
In this case the "actor" was referring as a role in the industry so more about an aggregation of metrics I guess.
Counting Minecraft and Tetris as American games? I suppose Microsoft bought Minecraft and EA licensed Tetris, but that seems to speak more to the business sense of American publishers than quality of American software development.
Eleven out of the twenty best-selling games are Japanese, and 28 out of the top 50.
The top 3 games by units sold were made respectively in Stockholm, Edinburgh and Moscow. How exactly do you figure that makes them "american"?
Also none of those are Japan.
No, but if someone e.g. dubs (and perhaps even recuts) a film for the local market, we would generally still consider it to be "from" the place it was originally made.
> Also none of those are Japan.
Sure, just trying to puncture the americocentrism a little.
And would it not be just as weird to say “designed in California” in the title of this webpage?
I don’t think anyone is questioning Japan having residents that can…fork Firefox. GP was questioning Japan as a mark of software quality, in an attempt to determine the intent behind the messaging.
It’a valid question. It’s a valid critique, even. There really is no need to get so defensive.
Maybe I'm just in the wrong bubble, but I've never seen that.
> And meanwhile, Japan has been the biggest video games actor in the industry for the latest 50 years
Japanese games are often notorious bad on the technical details. Their focus is on the gaming part. Though, it has become a bit better in the last years, but usually because Japanese Companies have diversified into international teams.
Maybe not everybody is flexing but at least people are not complaining about that, like for this web browser.
> Japanese games are often notorious bad on the technical details. Their focus is on the gaming part. Though, it has become a bit better in the last years, but usually because Japanese Companies have diversified into international teams.
So when it's technically bad, it's because the company doesn't have foreigners, when it's good it's because non-Japanese people are working there. Noted.
You have to be from a parallel planet or a limited bubble to not notice that Japanese games have always generally had fewer bugs than Western games, and much less need for patches, ever since arcades and the NES.
Elden Ring
Demon's Souls
Death Stranding
Resident Evil 4
Final Fantasy 7
Street Fighter 6
Final Fantasy 16
Armored Core 6...
Every major PS5 game in the last couple years, was virtually flawless on release day.
And of course Nintendo is still scoring hits with almost everything.
Meanwhile on Reddit everyone is crying about the PC versions, of even PC-only games!
Starfield has been a bug ridden joke, typical of Bethesda, one of the flagship Western studios, still unable to improve their janky physics and cringey NPCs.
Diablo 4 gave me the only crashes I have ever seen on the PS5.
Harry Potter, Redfall, Immortals of Aveum... overhyped flops. Baldur's Gate 3 has been the only saving grace from the Western gaming industry that I can think of.
Devil May Cry 3 and Dark Souls 1 jumped to my mind immediately as notoriously bad ports. Even DMC4 and DMC5 have some problems. FromSoft games improved the quality of their ports on the other hand.
I do understand that Japanese mostly play on consoles but nowadays it's not an excuse anymore.
It's a hellish development environment even for Western PC-only studios. WHICH PC game has been free of bugs in recent times anyway?
While on the other hand pretty much every PS5 game has been basically flawless on release day.
>WHICH PC game has been free of bugs in recent times anyway? Most indie games that I played. AAA-games are bug fests not because of the platform but because of the negligence by the developers.
Fewer features, fewer bugs.
> AAA-games are bug fests not because of the platform but because of the negligence by the developers.
Meanwhile most AAAs in the last couple years from Japan have been flawless on consoles since launch day.
>most AAAs in the last couple years from Japan Fewer games, fewer opportunities for messing up. On PC FromSoft games had problems with optimization (Elden Ring).
https://en.wikipedia.org/wiki/Video_game_crash_of_1983
Guess which hemisphere was responsible for the Video Game Crash and which one helped the industry recover from it. :)
Exactly. The developers are probably proud to have built something (presumably) high-quality in Japan and they want to promote that fact to help shift the country's image I guess.
- Dense interfaces, flashy colors, the opposite of Apple-style minimalism
- Proprietary software
- Lots of customization when its comes to appearance / theming
- Passionate communities
- Traditionalism, resistance to change
- Function over security
It does not all apply to Floorp, but that's what I think when I think of "made in Japan" software.
For example, Floorp is open source, which I think is less common in Japan than in the west, and hopefully, it is secure. But the customization and "dual sidebar" (i.e. more stuff on screen) features are typically Japanese.
(Now, this being HN I'm sure someone will cite some counter examples.)
What I don't get is why this is your main and only takeaway. It's such an odd and surprising reaction.
When I hear, for example, that Linux is being used at a gov site in Brazil or Germany or France - I get quit excited. I like that the FOSS is making inroads in other areas.
With the dominance of Chrome worldwide, I am equally excited that a group of developers from another country are helping push competition in this space, driving home the message of privacy. Mozilla needs it... we all need it for the health of the internet.
These guys have been at this for a while (based on their github page) and have made installers available for the main three OSes. I'm excited to give this a try.
Well they aren't known for software at all, but the japanese are notorious about being sticklers for quality.
- librewolf (Desktop) [1]
- Mull (Android) [2]
- Iceraven (Android) [3]
- Mercury (Desktop) [4]
- Pulse Browser (Desktop) [5]
- Waterfox (Desktop) [6]
- Floorp (Desktop) [7] --> This submission
- Pale Moon (Desktop) [8]
- Mullvad Browser (Desktop) [9]
- Tor browser (Desktop - Android) [10]
This list is not inclusive. It probably contains the famous forks.
[2] https://gitlab.com/divested-mobile/mull-fenix
[3] https://github.com/fork-maintainers/iceraven-browser
[4] https://github.com/Alex313031/Mercury
The PaleMoon team however forked even Mozilla Gecko ( https://en.wikipedia.org/wiki/Gecko_(software) ), the browser engine that is at the heart of Firefox to create the Goanna browser engine ( https://en.wikipedia.org/wiki/Goanna_(software) ) that now powers the PaleMoon browser and the Unified XUL Platform (a framework that can be used to create multi-platform desktop applications with web technologies).
Another "hard" fork of Firefox Gecko is the Servo browsing engine ( https://servo.org/ ) though no browser application has been built on it yet.
- https://news.ycombinator.com/item?id=16318820 (they later described this incident as "resistance from the BSD community to adhere to normal free software development practices")
- https://www.reddit.com/r/palemoon/comments/pexate/pale_moon_...
Also, I find it slightly amusing how often they bring up the legal aspect of these licenses. They're not wrong, of course, but are they really going to hire lawyers to go after someone like Feodor? At most maybe they'll get it removed from Github and other platforms that care to respond to such requests?
> You think trademark law is a joke?
Personally, yes :)
I suspect that they don't attract the best contributors, given how hard they seem to be to work with.
I'm not sure that's the reason. Regardless of feelings users may have toward developers, they'll still use the best tool for the job. I used Pale Moon on an older computer because none of the modern browsers performed well, including FF. I was well aware of some of the drama.
(Likewise, I raged against Microsoft for years before I made the switch to Linux. So many other examples)
When Mozilla went Quantum, it's performance was so good, it was able to replace Pale Moon. I wrote a thing about this here in 2019: https://news.ycombinator.com/item?id=19367536
I'm thinking that over the last 4 years (since 2019), many users have upgraded their hardware and the need for Pale Moon - as a lighter browser alternative - has simply diminished.
That said, none of this is scientific so I will leave it here.
And 500 is just my actively loaded tabs. I have another 500 suspended.
I'm really happy to see developers taking an active interest in modifying/forking FF. I was beginning to believe that interest in FF was dying out and so I'm finding this submission, as well as this list - extremely exciting!
[0] https://support.ablaze.one/articles/floorp/who-build-floorp