The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
It's not elitism, it's "On Error Resume Next". Any language which supports that should be strung up and whipped ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
Just never use "On Error Resume Next" and turn on Options Explicit and Strict. Easy. I much prefer C#, but I spent years in VB and then VB.Net and never understood the hate. Still don't. If the hate is because of the capability of misusing it, I can do that in C# too. Or maybe it is because it has built-in settings that are questionable to non-VB users (Explicit and Strict)? Maybe I'm missing something. But I don't care as I don't use VB anymore (since 2005). I prefer C#'s syntax. On the other hand, if someone could explain the reason VB is so bad (without the hate), I would welcome the education. Send me a private message or point me to a well-written post.
nothing wrong with VB.net, except MS decided to stop growing the language; about that time I decided to fully switch over to C#.
I worked in VB (classic) for years and got a lot done, it was a great way to get a quick UI working that worked. plenty of hooks to tie into the lower API of windows and c/c++ libraries. when .net came out, it was a no brainer to switch.
if it wasn't for Android, I'd never touch Java again though, just something about that language that I find painful. no offence to Java devs out there, it's just not my cup of tea.
Why not let the page designer interact with the layout engine instead, as it is laying out the elements on the page?
So now you've turned your four hour project into a sixteen hour project, because you have to write the code twice, and test it in all the different versions of the browser implementations of your new system, as well as all the browsers that don't support it. (It's already bad enough if you still need to support browsers which don't support modern CSS layout, but thankfully those are vanishingly rare these days.)
Plus every new browser needs to support both systems, since you can't reasonably expect every site on the internet to upgrade to your new system at all, let alone overnight. Which introduces more bloat, and more bugs, and more cross-browser inconsistencies.
If PSL96 had been implemented instead, CSS would be a lot easier. You simply express sizes of things in terms of sizes of other things. It would have resulted in a much smaller language, that most people could grasp. And people would create libraries of handy expressions that accomplish the very same things that flex and grid does today. With the huge difference that you can look at the code and see what happens. Right now it is just a back box that almost no one understands.
Browser support would be easier and more uniform, not harder, because there is a smaller feature set to implement.
Do you know of any other language where there is so low predictability of outcome? You basically spend your time trying 100 different tweaks until it looks right.
simple math formulas into the CSS, that refer to the sizes of other elements.
The good news - since it requires some basic math skills we'd see a drop in the number of (so called) designers.
The bad news - it's still potentially overly complicated and allows for possible feedback loops.
My guess: if it worked as you wished you'd be making the same complaint.
I'm not talking about clever ways to generate complex CSS, I'm talking about expressing relationships between page elements that is not possible at all with current CSS.
For example: "The height of element B is 1/10th of what ever the page height is at the moment. The width of element A should be equal to the height of element B, but only if B's height is less than 100px, in other case it should be half of the height of element B.".
Here is how simple it could look in theory: B.height = PAGE.height / 10; A.width = B.height < 100px? B.height : B.height / 2;
The reason stuff like that isn't possible is because you will get endless recursion.
Let's say you have:
The height of B is determined by the content of A, but if you are changing the width of A based on the height of B then the height of A will also change, which in turn forces the height of B to change, which would then require the width of A to change, which will once again change the height of B, and the loop continues until you get a StackOverflow exception.
So perhaps you say: "Well, don't allow rules like that", but then you end up with even more of a headache trying to make sure your rules don't conflict with other rules.
Put it this way, if it was possible to make it work well then it would for sure already exist.
As the saying goes: if you have a good idea, it either already exists or it really isn't that good an idea.
What you describe already happens in the layout engine of modern browsers. The rules that I outlined earlier already happen, but is invisible to us. There are hundreds of such rules that must be evaluated to produce the final layout, and some are in direct conflict with each other, so the engine is designed to make a compromise. These compromise heuristics is what avoids endless recursion.
So imagine that tomorrow the Google Chrome team launches a new module called JSCSS, were they have moved out all those heuristics from inside the layout engine and written them in JS. From now on you point to a JSCSS file at the beginning of a HTML page, which defines all the CSS rules you intend to use. CSS still works exactly like before. But the HUGE difference is, now you can see how a flexbox actually figures out layout, AND you can extend CSS with your own definitions for things you think is better than the standard. AND you can omit CSS altogether, and write your layout directly in JSCSS of you want.
This would be a huge relief for everyone, because browser makers only have to make sure the core layout engine works correctly, and every CSS definition is in external JS, exactly the same for every browser. And any developer can extend CSS with his own definitions.
That feature doesn't exist, because IMO it's something that we shouldn't do to begin with. Websites are displayed on various screen sizes, contrary to Windows App which almost definitely shown on a monitor.
If you fixed the size of element b as 1/10 of total web page's height, it will be nightmare/unreadable on some screen sizes.
If it's screen size, there already "vh" and "vw" as unit size.
Whilst I don't disagree with you re:CSS, in that example you've given it could be easily achieved using JS / jQuery.
It's simply a case of picking the right language for the job.
Of course as others have picked up on, doing that might cause all sorts of strange behavior once you start looking at the various sizes of screens your page may show up on, from 1 inch watches to 100 inch projectors. You just can not be sure of the scale your user will be using.
Like this[^], you mean? The calc() functions in CSS are useful, potentially (though I've not used them myself) but they don't directly include the ability to refer to other elements. However you can refer to CSS custom variables which may give you the flexibility you want. But hey, all this is just adding more bloat, and making it harder to learn (and test for cross-browser compliance). The trouble is, the features you want are not the same as the features someone else wants - and pleasing everyone is what leads to bloat in the first place.
It's a language by committee. And a committee made up of teams that are actively competing with each other. Read this discussion on CSS4[^]. They actually, deliberately, don't want to increment the CSS version anymore. That's like macOS stopping at version 10 (...but instead is 10.1, 10.2 etc), and Windows 10 stopping at 10. Or 10 20H1, 20H2...)
I think the hardest part of CSS is the "C" - the cascading, which relies on Specificity. It's super logical and very well defined. And an utter nightmare as soon as you step off the beaten track. Switch elements around, decide you need some special formatting, try and generalise it, and boom!
Still - it does at least attempt to encourage a separation of layout and style. Except the CSS defines the layout