Daily Shaarli

All links of one day in a single page.

December 29, 2024

Note: Becoming a good enigneer

Most people can do that (become a software engineer) but NOT EVERYONE can become a good one. To be a good software engineer, the most important thing is that you try to understand things how it works, you really really try hard to understand HOW IT WORKS, MAKE IT WORK — XT at Google

Getting Started - schema.org

Getting started with Microdata

Outil de validation du balisage Schema

Validate microdata markup

Try with https://alandalton.github.io/Authors-Apart/ for example

HTML Standard

The specification of microdata

How do you do, fellow web developers? A growing disconnect. | exotext

The author feelds a disconnect with web developers who knows only JS frameworks to build a website as SPA...

What if Schema.org is just… Labels? - Jono Alderson

About microdata:

Labelling things properly is still a powerful act, especially when it involves repetition and relationship-building.

What the post is missing is: how building these connections are useful? Ok it's great for AI models that are parsing the site...

Why I love Rust for tokenising and parsing | xnacly - blog
I Almost Died for a Full Sentry Database - IT Notes

One dev thought it would be a good idea to put everything into the cloud without estimating the bill :-D

Fish 4.0: The Fish Of Theseus

Pain in C++

  • tools and compiler/platform differences
  • ergonomics and (thread) safety
  • community

Why Rust?

  • fun & cool: better for a hobby project. It is a need.
  • Great tooling
  • Options are easier to use than C++'s pointers
  • use system over #include
  • simpler dependency management
  • killer feature is Send and Sync, statically enforcing rules around threading.

Ship of Theseus strategy for the rewrite: component by component. The fish app should work exactly the same.

So if you are trying to draw any conclusions from this, consider the context: A group of people working on a thing in their free time, diverting some effort to work on something else, and deciding that after the work is finished it actually isn’t.

Gripes with Rust

  • portability between OS: it allows to miss systems and ignoring version differences
  • string translation and localization: format! are checked at compile-time
  • building to other targets: "it is often better to use if cfg!(...) instead of #[cfg(...)] because code behind the latter is eliminated very early, so it may be entirely wrong and only shows up when building on the affected system.

They also report mistakes they made.

There are good with quick-wins of the port to Rust. There is also some sad ones: CMake is not removed yet. Cargo is missing some features to install third dependencies (.fish scripts, 130 pages of documentation, the web-config tool and the man page generator).
Cygwin is not a supported platform.