</sarcasm>

Travelled 4 hours to an interview to do a JavaScript paper test with questions copied from W3C academy👌

We want this <sarcasm> tag w3c 😀

10 year challenge

The new w3c standard "CSS Houdini" gives you access to the css engine and let's you write your own css properties. That means no more polyfils, new exciting website designs and more possibilities and control on how the css is rendered on all browsers.

Please. Hear me out.

I've been doing frontend for six years already. I've been a junior dev, then in was all up to the CTO. I've worked for very small companies. Also, for the very large ones. Then, for huge enterprises. And also for startups. I've been developing for IE5.5, just for fun. I've done all kinds of stuff — accessibility, responsive design (with or without breakpoints), web components, workers, PWA, I've used frameworks from Backbone to React. My favourite language is CSS, and you probably know it. The bottom line is, you name it — I did it.

And, I want to say that Safari is a very good browser.

It's very fast. Especially on M1 Macs. Yes, it lacks customization and flexibility of Firefox, but general people, not developers, like to use it. Also, Safari is very important — Apple is a huge opposing force to Google when it comes to web standards. When Google pushes their BS like banning ad blockers, Apple never moves an inch. If we lose Safari, you'll notice.

As for the Safari-specific bugs situation, well… To me, Safari serves as a very good indicator: if your website breaks in Safari, chances are you used some hacks that are no good. Safari is a good litmus test I use to find the parts of my code that could've been better.

The only Safari-specific BUG I encountered was a blurry black segment in linear gradients that go from opaque to transparent. So, instead of linear-gradient(#f00, transparent), just do linear-gradient(#f00f, #f000).

This is the ONLY bug I encountered. Every single time my website broke in Safari other than that, was for some ugly hack I used.

You don't have to love it. I don't even use it, my browser of choice is Firefox. But, I'm grateful to Safari, just because it exists. Why? Well, if Safari ceases to exist, Google will just leave both W3C and WhatWG, and declare they'll be doing things their way from now on. Obey or die.

Firefox alone is just not big enough. But, together with Safari, they oppose Google's tyranny in web standards game.

Google will declare the victory and will turn the web into an authoritarian dictatorship. No ad blockers will be allowed. You won't be able to block Google's trackers. Google already owns the internet, well, almost, and this will be their final, devastating victory.

But Safari is the atlas that keeps the web from destruction.

I've been calling the W3 Consortium every day for the past week leaving the same message:

"Why the fuck doesn't CSS "vertical-alignment" work on all elements?"

Still waiting for them to return my call..

WebVTT: Can I copy your homework?

SubRip (.srt for friends): ehm...ok, just change it up a bit so it doesn't look obvious you copied.

WebVTT: don't worry.

Straight up there 😂 No sugar coating.
Nice guys at W3C lol

DatePickers should be a W3C standard handled by the browser. We shouldn't rely on JavaScript plugins to do this basic input stuff

Then: World Wide Web
Now: World Weird Web

Fuck you apple, and fuck your god damn shitty documentation.

Working with NFC enabled passes, their documentation says "payload max is 64 bytes"

What they ACTUALLY fucking mean is 64 ascii characters.

Also, the way they handle date time formats is fucked. They say they support W3C formats (iso) but what they actually mean is, they support a half assed version of a subset of it.

I told their chief engineer over a phone call and his response;

"I agree, our documentation is lacking"... HOW ABOUT YOU FUCKING UPDATE IT!

Also, how they handle json is just bad.

How many web devs support this 😂

1, People stop forcing Node.js on me
2, Browsers actually comply with W3C and don’t publicly experiment on their own
3, Internet Explorer is pulled from all installations retroactively

Just a thought, but aren't all those "looking glass" 's, as abusable as w3c checkers to mass flood for free? there's atleast a thousand of those and none of them have any limit in place

The W3C HTML validator just told me to add a lang attribute to the <html> tag on my website. Apparently it didn't notice, that the <html> tag was missing.

My image of dream career through different times of my life:
- frontend specs prodigy, css enlightenment, a member of w3c or a similar committee
- indie hacker and entrepreneur, leader of a startup community
- architecture prodigy, expert in scalability
- transsexual evangelist, popular article writer and a rockstar
- hardware engineer: Linux, C, chip and dale’s Gadget-like girlfriends, xkcd, latex, assembly, buying a radio station and a telescope
- scientist like NickyBones, papers, data, more data
- art expert

Though achieving one of this would take the entire life, I had a chance to grasp all of this. WHY does they feel so incompatible? Why do I have to choose?

Why do I feel so sad? Why do I feel like I haven’t achieved anything even though I objectively achieved what I dreamed of like five years ago?

Is it true that it’s in my nature to always seek an environment to feel like a junior in? Is feeling like a junior only pleasant to me because it reminds me of old times when I wasn’t actually this mentally ill and was still happy?

Why do I feel like that arduino and C shit is the equivalent of a red corvette?

Hey guys so we need to start taking accessibility seriously, it’s the law - right now we currently do nothing.

So let’s start with something super simple. Alt text has to be provided for an image...

“This is all bollocks let’s be honest”

😳🤦🏻‍♂️

Um...so I don’t make the rules, the W3C define the standards for the web. Disabled users matter...

the more i learn about web dev, the more i realise the reason for its mess up . There are 2 major problems in it : the people who create various important concepts and tools for web dev were 1) working on it without any collaboration and agreements on the philosophy and 2) were too stubborn on their ideology i guess.

There is no limitation to anything's functionalities, and the limits that are "defined" are badshit crazy. for eg:

====================================
HTML creator : "I am gonna make a language that would provide a skeleton to web page. it will just have the text and basic markers to let the scripting and styling engines/languages know which text is supposed to be rendered and how.
It won't provide any click or loading functionality.

someone: "So i guess opening a page or loading an image would be handled by JS or other programming language? also, bold , italic or division would be added via CSS?"

HTMLguy : Nah, my html engine would ALSO do that.

someone : what , why? won't that just be stupid and against your philosophy?
HTMLguy : WHAT? am too awesome, can't hear you
w3c , 50 yrs later : sorry can't change this, gotta support the 50 yrs of web dev and billion sites

=================================

CSS guy: I am gonna make the world's best beautifying stylesheet language to provide colors, styling, fonts and backgrounds to a page. every loadings and clicks would be handled somewhere else

Some1: cool, then clicks, hover and running of animation would be handled by JS only

CSSguy :Umm, i guess i could handle those.

Some1 wha-?

CSSguy : Thankyou Thankyou Thankyou for the nobel price!

====================================

JS guy : I am gonna make a god web programming language! It can do everything: add/remove html tags, add styling, control animations, control browser, handle clicks , perform operations, everything!

some1: cool! you must be making very large programming language with lots of modules.

JS guy: No! i am gonna keep it small. no built in classes and file imports! just use the functions directly. if someone wants the additional lib functionality, install them on your server

some1 : innovative! what's typeof NaN ?

JSguy :shut up.

Best? Clojure docs. They have disqus-like thing under every function description where anyone can submit their usage example. One example times forty submissions equals forty examples!

Also w3c specs, nuff said.

Worst? GunJS. Multiple websites that look like each other plus GitHub wiki all with the same content but idk which one should I use, also there is no complete source, you have to look up everywhere. Also NextJS, they’re too busy pitching to investors, there is no way of contacting them, you’re in your own if you choose nextjs, that’s why I banned it everywhere I have the power to ban things

<anchor link> for `tel:` makes no sense to add a title tag but you almost have to so I add title="tap to call"> which of course will never get seen by a phone DOM. Hmmmm, what say you W3C?

What's the fucking point in having a W3C WG if browsers are just gonna each implement it differently in fits and starts taking fucking years before it can actually be used in production?!

😡😡😡😡

I want to use SVG2 before the end of the decade please... ffs!!

One of the most inefficient practices I've seen done in companies is the company housing 50+ devs having to hire an expensive consultant who is only available on a limited time to figure out mysterious or in-depth problems with the company's main application (for example, JavaScript problems).

Then the whole dev team sits on his shoulders and production can't run smoothly until he fixes things. Even worse, him having the so-called qualifications, being the 'expert', but when asked an in-depth JavaScript question, they don't know the answer.
When I suggest to figure out things in-depth so problems like these can be prevented in the future, I'm met with: "Nah bro, we'll just apply quick fix #2" just because I carry the title 'Junior Developer'. Makes me want to hit my head on the wall on how stupid these people are.

This could all be solved if the dev team would be competent in the first place, knows how to read documentation and isn't lazy, most importantly. I hate teams like that.
Grab, the damn, documentation, read W3C, read MDN, get educated, and stop using band-aid solutions! Gah.
Toxic companies like these are what's wrong with some places in the development world.

I'm a proponent of knowledge.
Fellas, know your stuff.

!rant /* but */ is funny == true

Developers! - should browsers forgive you ?
Or put a curse on you so you can never align your elements like you want to ?

You will know you don't want it there and it will annoy you, it will eat you inside looking at that webpage..

Again, W3C guys being straight up no sugar coating 😂😂😂

You can say you know a computer language to a decent level when you can in fact make useful programs with it.

For example, I can say I know JavaScript to a basic level. I know its basic core functionality by heart (which can't be said for some people I know), such as:

- it manipulates the DOM, the DOM has Element, Nodes, TextNodes (all to be found on W3C documents with its own specs)
- useful functions are:
getElementById()
getElementsByClassName()
Also knowing that these return either HTMLElementCollection or NodeCollection because you have to iterate over it differently then
- element.textContent
- == and ===
- dynamic typing
- closures
- avoid global variables
- nodes have parentNodes
- isNaN, undefined
- arr.push()
- arguments don't have explicit types defined
- etc.

Using this knowledge I built an antispam script for a particular server. It's good to know the model of a language, that it sits in your head and that you can use and understand the constructs when you want and how you want.

I wish it was :
"URIs don't change, people change"
Original quote by Tim Berner Lee
(correct me if I am wrong)

Stumbled to this page while reading Django URL dispatchers...

web components are the best components

I just came with a problem trying to get the value of an HTML input of type date and trying to throw it into a Javascript Date object... After about an hour of searching (Google, Stackoverflow) I realized HTML5 date inputs use UTC timezone (defined by W3C) and Javascript uses your local timezone and this difference is messing with my code giving me a JS obvject 1 day before the HTML date...
Why they do this kind of thing?

Day 3 at the office:
Still no project, I read about AngularJS yesterday, today I am reading JavaScript on W3C.
For some reason I have Internet access from IE and Chrome, but not from FF... :-/

The guts, i mean WTF?

Tried learning client side storage and the lord of the best practices (google) were like "WebSQL deprecated,use Indexed DB instead".. said fine,im up for skill level-up

...

That was 2 years ago and WebSQL is fully supported upto Android 7.1 yet i dont see no buzz about indexedDB, user s i have to support are mostly on Android 5.0 (which has excellent support)...come on...pick a side and leave devs out of your batshit crazy politics.

jinja templates make me look towards html in a whole new light. are we 'inserting' data to an already rendered page? am i really mixing server code with ui ? It doesn't feel so. there are if else and loops being executed for html code, like wtf?

I don't know but everything feels so good. like i was literally hating every piece of website i was writing in php. everytime i wrote <div>....</div> followed by <?php ... ?> followed by another html tag /php tag in a fuckin php file, i wanted to kill someone from w3c.
WHY THE FUCK ARE WE ALLOWING THE MIXUP ?WHY IS PHP FILE HOLDING HTM TAGS? WHY?WHY?WHY?

But this... this is beauty. their is separation of concerns. jinja has some big powers, we can loop, repeat, make clauses, inherit other html classes, load html content into blocks, set variables,
but main concepts like file handling, response/request handling,calculations,etc are all being done in separate python files. I know that these jinja templates also might be running python in background, but atleast a developer cannot fuck up that code.
we can be sure that if correct jinja codes are written in html, then it would load correctly. And wherever devs doesn't fuck up, the output is better to understand and more maintainable/scaleable

Read The Docs!!!
Read The Docs!!!

But none of y’all have read the ECMAScript Specification.

Don’t even get me started with W3C… Just stick with your W3Schools

The W3C EME DRM debacle...guess we'll need a new internet soon 🤔

Web devs, let's be honest. When was the last time you checked your HTML's conformity with W3C specs?

So for the special kind of event handlers that runs before an event, would you prefer the react style "will" as in "onWillChange", or the W3C style "before" as in "onbeforeunload"?