- cross-posted to:
- webdev@programming.dev
- cross-posted to:
- webdev@programming.dev
You must log in or register to comment.
* { display: flex; }Oh wonderful! Another 10 years and we can use it natively without polyfills!
It’s already supported by
96%87% of browsers currently in use.
Can we not do away with CSS/JS, learn from those mistakes and try something else? Pls, I beg you 🥺🙏
E: Sorry, forgot the /j Lighten up, Lemmy, not everything is a serious comment that needs your scrutiny or meticulous rebuttals.
What would you replace it with? There are lessons to be learnt from the web, but to “fix” it is much harder
Flash and applets. Let’s just have a do over of the 90’s and early 00’s.
/s
Please! I miss my Action Script 3, not this cheap wannabe TypeScript 😭
i did valign years ago. /s
also i think more needs to be said about a push to localise css (and html, really). the fact that it still requires programmers to be versed in english is pretty sad.
English is the most spoken language outside of its home country and it uses the simplest alphabet.
It is a pretty sane choice.
You could write yourself a nice preprocessor
It’s a simple alphabet for computing because most of the early developers of computing developed using it and therefore it’s supported everywhere. If the Vikings had developed early computers then we could use the 24 futhark runes, wouldn’t have upper and lower case to worry about, and you wouldn’t need to render curves in fonts because it’s all straight lines.
But yeah, agreed. Very widely spoken. But don’t translate programming languages automatically; VBA does that for keywords and it’s an utter nightmare.
Or worse, Excel, which translates the function names but doesn’t do it automatically, so you can only open a spreadsheet if your Excel is configured to the same language as the spreadsheet was created in.
English source code is a universal language.
I’ve never seen a need for localization beyond domain terminology. And I think it would be a huge detrimental.
To implement it would be unnecessary significant complexity. Effort better spent elsewhere. And for programmers it’d be confusing. Think code snippets, mixing content, and the need for reserved word expansion or exclusive parsing scopes that would be even more complex and confusing.
