>I wonder why exactly this is posted as a google translation of a portuguese article.
He was/is hospitalized in Brazil.
217 karma · joined May 6, 2015
He was/is hospitalized in Brazil.
*Update:* Oh and it's interesting, "rubi" was used but the W3C recommendation from 2001 made "ruby" more common as spelling.
Even when ruby markup is popular with south-east asian scripts I mostly want to use it for interlinear text or textspan-level inline annotations for a software to learn languages.
I remember with the ruby specified in XHTML standard there were ergonomic issues when ruby is written, i.e. it's nice for interlinear text markup to not have to close HTML tags. Also there were issues where people did not understand what the differences between mono ruby, group ruby and jukugo ruby is (correct me if I remember it wrong).
Ruby seems to be not implemented well in browsers, some ruby-related tags were deprecated, the specification posted is part of the restoration of these tags [1]. But last time I checked there was interest of all major browser manufactors to implement ruby standard properly.
A deep rabbit hole which started for me when I read Paul Watzlawick in the late 90s.
(the German Wikipedia article about it is much more detailed than the English one; I guess it's good to read using machine translation)
*Edit:* Ahh I see, capitalized not uppercased.
I've been using Windows for two decades and before that I loved the Amiga Workbench.
When I had the choice between a Dell Windows notebook and a macBook I went to the Apple store and some enthusiastic person showed me the new 2017 models with larger touchpad and gestures to move between workspaces. I thought "these apple people. who needs that".
Then we ordered the macBook and because of my keyboard layout choice it took a week to arrive. I got a used Dell notebook for week, worked and then switched to the macBook.
When I had to give the Dell back I wanted to transfer some files to the macBook, and I used the touchpad and made some macOS gestures and wondered why the touchpad is so small and why the gestures don't work. This was the moment I understood why the person told me about these things.
I'm using macOS for 7 years now. Also had to deal with some bugs and stupid UX here and there. But overall my OS of choice for sure. Oh and the touchbar on the top of the keyboard was not even a good idea, I think. My last Windows was Windows 7 and I liked it a lot. Windows 10 I never liked, even when I only used it in a VM.
I'd say you almost never need file-based routing, I'd even go that far to say you don't need routing DSLs for backend (just use if statements, performance will be fine without compiled regular expression to match all routes). The fetch API has request and response objects, and URL and URLSearchParams. But in frontend I find react-router-dom very practical. I think they introduced file-based routing in NextJS and co, because it's easier to generate frontend code bundles per route by listing files at build time. Other than that it's just a gimmick.
And as already mentioned ORMs (object-relational mappers) will give you headaches really soon, it's probably not worth it.
You can use Vite for the frontend part which is more lightweight than NextJS and co. I'd say if you have or your team has already build a web application with such full stack framework once you probably know what is needed and what is not needed in frontend with Vite.
Yeah, it's a bit implicit. Or you have to learn the rules by heart.
I also saw people struggle with two elements aligned to bottom with different line heights. Turned out they did not know that there is a default line height. And of course the "correct" line height to use is either "1" or "1.15" (not the browser default).
The written Tailwind code might not be beautiful (still it tends to be simpler than well-constructed CSS), but it does not stop the resulting website from being beautiful.
Well-constructed CSS does not stop one from building non-beautiful websites with beautiful code.
You can also complain about JSON being a mediocre data format. But I think it's minimalism and compatibility with JS made it successful.
This is related to `React.createElement`, I think. Preact does not have this problem. For client-heavy web applications I prefer React over Preact (not all libraries work well with Preact), but server-heavy web applications are fine with Preact.
Using Razor obviously did not stop Microsoft from building buggy web applications.
If a condition in JSX gets too complex I normally extract a component-level function and call it from the JSX part of the component.
JSX is a nice templating language. And when you use Deno or Bun you can use it directly on server-side. My server-side components have no hooks and use preact-render-to-string or `renderToString()` from `react-dom/server`.
Also there is Gatsby which is a popular content management system which also allow non-interactive statically rendered pages (as far as I remember).
React rendering can get very very slow. A classical example are inputs that update very slowly when you type something. "Best practices" lead us many times to this when we round-trip the whole state from input change event, to global store object, immutable changes and back to the input. You can fight it with React.memo and by just mutating the state in-place.
Recently, I found valtio helpful as it allows to hook React components to rendering for parts of the global state.
Also all this useEffect(), useLayoutEffect(), and when it's not enough useEffectEvent() [1] and useEvent().
[1] https://react.dev/reference/react/experimental_useEffectEven...
When you go to the page:
- first line: "Adaptive..."
- second line: "The adaptive..."
- third line: "...adapt..."
Then the next block:
- "flexible and adaptable"
>FAST provides an innovative theming system called Adaptive UI, which builds design system properties that designers use every day directly into every component.
Then the next block is an example where you can change neutral color, accent color, saturation, border radius, stroke width and density of all components in a frame on the fly.
>like bootstrap, tailwind, chakra, material, semanticui,
In order to adapt all components you have to
- in bootstrap edit SCSS variables
- in tailwind edit tailwind.config.js and probably use CSS variables for the utility classes you use
- in chakra override global CSS styles in the style object
- in material v3 define your own baseline and dynamic color schemes
- in semantic UI override CSS in your theme.config.
But it seems only tailwind with CSS variables allows to change styles on-the-fly, i.e. more than just toggle between light and dark mode.
*edit:* formatting
But Azure DevOps and Microsoft Teams make me think that the Microsoft engineers working on these products absolutely don't care and they probably don't need to care, and the companies using these products also don't care.
Popularity and dominance are criteria for success. Their success, but not necessarily your success. If the product is by Microsoft you have to look more than twice if it's a good product or if it's close to self-sabotage when you use it.
Anecdote: One of my coworkers once thought that Dutch means German. I guess it was because the words "dutch" and "deutsch" look so similar.
>Fringes can track the value of benefits or fees that are required above and beyond the raw cost of labor or materials. Fringe benefits could include employment taxes, fees for pension & welfare programs, or daily charges for a given resource. They might also include allowances for holiday or sick leave funds. >Fringes can also be used to track things like sales tax on materials. >Many employment benefits have a limit or cap for how much total compensation an employee can make before the Fringe benefit is cut off in a given project.
I assume in the newer trains they already recreated new systems. For the old trains it's just not worth it to modernize, as it's incompatible with the newer trains and thrown away eventually.
And who knows, maybe they gave it a try in the past, and it did not work out.
What you wrote reminds me a bit of a friend who asked me 15 years ago when he installed Java: "Who uses Java anyway?". You just have to change your perspective from an end-user. Same for Windows 3.11.
They used and still use MS-DOS, Windows 3.11, Windows 95, and Windows NT for different systems over the years in the older trains starting from 1989 to estimated 2030.
>Remote: Windows 3.11 Administrator (m/f/d).
Why do you assume that? The Siemens SIBAS 32 system can be used at home, and an old PC system with Windows 3.11 should be the smallest problem to use at home. The question is, if that's enough to simulate an environment similar to the train.
When you look at the software and AI, the German car manufactors are ahead of say Tesla.
*Update:* Yes, looks like it uses the networking stuff provides by MS-DOS.
MS-DOS has NETSTART.BAT and PROTOCOL.INI that initializes TCP/IP with IP address and subnet mask.
When you look how a passenger information system in the trains boots up you can see how it shows BIOS information (floppy drive connected, serial and parallel port available, no harddisks) then it boots MS-DOS, initializes a XMS RAM disk, initializes parallel port, loads Crystal ENDS2ISA ethernet drivers, microsoft DOS TCP/IP protocol driver, and TCP/P MEMM driver, and calls NETBIND.COM.