290 karma · joined July 28, 2022
Or if you have a choice of markup language just use XML.
You can’t have your cake and eat it too, either use XML and deal with the verbosity or use something else with less markup but more error prone.
I personally prefer XML as verbosity is the least annoying problem to deal with.
The 5 year limit is regarding not having major/breaking changes.
I think people who are social (media) butterflies and/or are opinion leaders on social issues are affected the most by the degradation of content moderation as the more you engage the public the more the public engages you, including all the unsavory elements.
If you, like me, just use Twitter as some sort of glorified/souped-up RSS feed, then nothing’s really changed. I think this is the healthiest way to engage with Twitter anyways.
So that aspect would not be OSS.
So I guess the conclusion is that Unity was fucked pre-IPO?
You think the management made a mistake, I think the management (as a result of going public) is the mistake.
The argument hinges on the premise that Epic, who operates their own game store and is courting developers aggressively with generous revenue split, is willing to burn their bridge with developers for questionable increase in profit; in addition it presumes that the plain old revenue share model that Unreal Engine utiltizes makes less money than this so-called runtime fee.
I beg to differ, I think the only reason Unity went this route is because they don't want to be seen to publicly break the promise of no revenue share/royalty pledge they had earlier, and ironically came up with an even worse monetization scheme.
In my opinion, the only reason this whole fiasco happened is because Unity the company has too many headcounts and has too much expense, and the reason for that is they grew too big, and the reason they grew too big is because they took the company public and in that sphere success is measured in growth, even if the company is much healthier if it had stayed smaller.
Epic is privately held, Valve is too, Unity is not and we ended up here. I think that says a lot.
Just vote with your wallet and switch engines, optionally (ideally) donate to open source projects like Godot.
I seriously doubt even if IA lost a bunch of lawsuits would your archived website be in any danger, as there are many many interested parties (including nation states) who are keen to keep the archived websites from disappearing as they are an important public resource.
I’d bet that the Internet Archive will last longer than Wordpress as an organization.
Like a swan song that lasts way too long through sheer financial will.
It does things in a brain dead way to protect you from other people’s idea of cleverness.
Also in corporate settings apps and sites don’t follow sensible rules, you think you’re gonna have a few sensible classes for a few different components?
Well marketing decided that they need 50 small variations of just one component, of course it makes no sense to you, but that’s the requirement so shut up and do it.
If you’re not using Tailwind you end up with 50 exceptions and your normal CSS quickly becomes unmaintainable.
Tailwind is the mad solution perfectly suited for a mad world, and only people who hate it are those who don’t have to deal with madness.
The alternative is not sanity, but simply unmaintainable madness.
Because nobody can guarantee the later even if it’s a paid tier, much less a no-cost loss leader.
But if I'm going to use a quirky framework, I'd rather use my own.
It basically kill competition and helps big players.
That’s actually not what happened.
Images have their baseline at the bottom edge, so Pill 1 is simply aligning its text to the bottom of the <img> element which is the first item in Pill 2.
You can confirm this behavior by enlarging the image, you can see Pill 1 shifting vertically to align the text baseline to the new bottom edge of the image.
You can also swap the order of the <img> and <span>Pill 2</span> so that the text goes first. You will see that they will now align despite the fact that the inner text is supposed to be “hidden”.
An easy way to solve this is to give .wrapper a hidden pseudo element with a bit of text so it becomes the first item to be used for alignment.
.wrapper:before { content:"a"; width:0; visibility:hidden; }
You can also just set the image as background to avoid the <img> element altogether.
Features like table is the ultimate conundrum - if you want beautiful text based tables like in reStructuredText it becomes very difficult to write and edit unless you use a specialized editor, while Asciidoc’s table syntax is very code-like and is completely unreadable as a tabular table (almost like a simplified HTML markup).
Markdown strikes a middle ground where it tries to be readable while being as easy to write by hand as possible. However in practice most people don’t bother to keep the columns aligned by hand so it still becomes quite unreadable, and you still need specialized editor to do align columns automatically if you want to retain readability.
You can consider it a good compromise or failing at both tasks (I view it as the latter).
Markdown is also wildly inconsistent - why have fenced codeblock feature with info string to set the language, when you can’t have fenced blockquote with info string to set the “cite” attribute?
I’m actually quite fond of reStructuredText but without widespread support it’s hard to justify investing into a much less portable format.
They’re not like the other companies listed.
It leaves gaps in the image for you brain to “fill in the gap” and add perceived detail.
Alternatively you can paint/airbrush every set piece to add that used/worn look, but I don’t think it’s economically feasible.
A bit ugly, but works.
Always limit your exposure and never keeping any amount of money with Paypal that you’re not prepared to lose in the worst case scenario, because Paypal is accountable to no one.