thr33

well this is not exactly unique to software. It is not a given that the 'handmade' nature of a product (luxury or otherwise) manifests in anything tangible or self-evidently superior. Luxury products in general overwhelmingly treat the crafted nature of the product as almost solely an investment in narrative (read: marketing) and market positioning, not an actual material outcome.

using text would lay bare the silliness of the radial menu pattern - it either wouldnt fit neatly into the circular containers or, if conformed to the curvature of the radial menu, would be unreadable/low accessibility

this approach is definitely more usable. radial menus only make ergonomic sense on ie game controllers. with a mouse it becomes a high precision action to use, plus poor accessibility because it doesnt conform to the standard box model.

complete disaster. terrible for your skin, feels gross, falls apart, and cannot be repaired. meanwhile my cotton pants that have been repaired many times are still treasured wardrobe items almost 10 years on.

rounded corners are actually a significant accessibility factor and powerful gestalt mechanism in design. The border radius of a rounded rect makes it discernable at a glance the boundaries of the element and what is inside and what is out. Concentric rounding can clearly communicate parent child relationships in an astutely gestalt fashion.

expecting to use cm/in for digital design is ludicrous.

(seemingly few) People bash it because its just writing regular css but objectively worse and incorrect.

if you can write tw you can write css. if you can write css theres no valid reason to write tw.

pdfs are categorically not the appropriate medium for this.

the kiosk factor is great to hear. Ive tourguided foreigners around several times in the past and having to wait on them to do everything seperately in the office always took the wind out of my sails when getting around.

the JR pass is almost never a good deal. you need to do a significant amount of travel over a significant distance in a short amount of time and is a very inconvenient way to travel compared to just using an IC card plus adhoc shinkansen tickets.

it is not only doable (trivially so for most static sites) but also the only appropriate model for delivering websites/software.

you can do everything you just mentioned with grid more reliably and by writing significantly less css than the flex method.

was just thinking this. work on a variety of complex webapps across multiple frameworks and you'd never catch me dead using css-in-js or a preprocessor.

I too love flex but your comment is a bit off. bootstraps grid system is a fake grid modelled on flex. building layout grids with flex in general is definitely not endgame, its actually very tedious and unreliable.

css grid however is perfect for this and represents one of the most underutilised powerhouses in the css kit

justify/align and content/items have specific meanings and the 'intuitive' naming most people expect - horizontal, vertical - completely betrays the powerful elegance of the flex model.

justify always refers to the main axis of a box model element, and align refers to the cross axis. by default, flex-direction is set to row, so justify often means horizontal and align often means vertical.

until it doesn't of course. when we switch tbe flex direction from row to column which is a very handy trick for easy responsive on small devices, the main axis is now vertical and the cross axis is now horizontal.

colorblindness would have no effect on this ux pattern