HenriTEL

The design might be great on your app, but I just had a look at the features page https://lighthouseapp.io/features and it looksquite messy. Too many of colors and information in the feature tiles, colors of icons in the section headers are off, alignment is odd. As a newcomer, understanding the features on this page takes a lot of efforts.

Among all macOS apps and their weird choices, finder is the most enigmatic one. The Recents tab sorts by Last Opened by default where I would expect to see the rencently added files first. Sorting by another column will not add said column to the view. Files from the Downloads folders seems to be excluded from Recents, or they take hours to be taken into account.

It does not show the current path, no button to go up the file tree, the only text input is behind this search button and it does not understand relative or full paths.

Well, thank god I have a terminal and an IDE at hand.

During Jobs era obviously design was a first order concern.

Then Cook took over but still Jonathan Ive stayed as head of design until 2019.

Ive was replaced by Evans Hankey and Alan Dye who were under Jeff Williams, the Chief Operating Officer.

Talk about a downgrade!

Apple already had serious contrast issues that have been adding up over the last few years, notably yellow text on white background or grey text on dark grey background. This liquid glass design will make the issue ubiquitous.

I'm working with python and it does not work very well, LLMs usually generates at least an order of magnitude more code than what I would write. That code often uses outdated practices, does poor design choices and does not understand hints like writing code in a way that reduce cognitive load, even when we explain that it means, i.e. keep the number of classes and functions small.

It's the complete opposite of OP's main language GO, as he says:

> Go has just enough type safety, an extensive standard library, and a culture that prizes (often repetitive) idiom. LLMs kick ass generating it.

Python is an interpreted dynamically typed language and the static type checkers are not there yet (most popular 3rd parties libraries have no type hints for example). Also it allows for many different programming styles that the LLMs struggle to choose from.

1. Every extra line of code is much more risky. 2. It's much harder to verify the LLM's code.

On the other hand I think rust will be in a good place in regards to LLMs in the next few years thanks to the robustness of the language and the quality of its diagnostic messages. Those 2 attributes should compound very well.

Yes, in the end, no matter how polished your apps are, a NAS is a tech product sold to tech people. Tech people want to choose their hard drive.

Web archive: https://web.archive.org/web/20250411060742/https://www.nytim...

All the magic seems to happen in

    const lib = b.addLibrary(.{
        .linkage = .static,
        .name = "cgo_static_linking",
        .root_module = lib_mod,
    });

and

/* #cgo LDFLAGS: -L./zig-out/lib -lcgo_static_linking -static #include "zig_lib.h" */

Now I can only guess why it works. A bit of an explanation wouldn't hurt. Good post btw

For marketing reasons, to justify value in the new gen of devices.

I must be to tired as I can't find any flaw in that reasoning.

What do you mean by being known?

That's far from my experience. Last time I used chatgpt it added many comments to explain the generated code and also attached rough explanatory text. You can also just ask more details about something, or to list other approaches, explain tradeoffs, etc. You can also ask for general questions to help you get started and find a good design.

To me it's about asking the right questions no matter the level of experience. If you're junior it will help you ramp up at a speed I could no imagine before.

Meero | Senior Back-End Engineer | Paris, France | Full-time | Hybrid/ONSITE | https://car-cutter.com

Meero develops 3 products to provide automated video and image enhancements to players in Real Estate, Automotive and Fashion worldwide.

We're looking for a Senior Backend Engineer to work on the Automotive app, car cutter. The team is still small but the product is growing fast. The candidate must be proficient with Python.

Read more: https://careers.flatchr.io/fr/company/meero/vacancy/bejyy9l7...

You can email me at myfirstname.hannetel@meero.com

But how will they sell their cloud storage then?

I did something similar a few months ago in python. One notable difference is that I got rid of the frontmatter, instead I use the commits history to find the creation and update dates of posts.

https://github.com/HenriTEL/gitblog2

From the doc it does not seem to be the case.

> Use beartype to assure the quality of Python code beyond what tests alone can assure. If you have yet to test, do that first with a pytest-based test suite, tox configuration, and continuous integration (CI). If you have any time, money, or motivation left, annotate callables and classes with PEP-compliant type hints and decorate those callables and classes with the @beartype.beartype decorator.

Don't get me wrong, I think static type checking is great. Now if you need to add a decorator on top of each class and function AND maintain 100% code coverage, well that does not sound like "zero-cost" to me. I can hardly think of a greater cost just to continue dynamically typing your code and maintain guarantees about external dependencies with no type hints.

I don't get the point of a runtime type checker. It adds a lot of noise with those decorators everywhere and you need to call each section of the code to get full coverage, meaning 100% test coverage. At that point just use rust, or am I missing something?

I agree, unless other exceptional conditions, having to go 5 days a week to the office is a strong no-go for me, FAANG or not.

The normalization of deviance around lack of sleep and experience if definitely the number 1 issue, but come on. That design to maneuver the ship was fucked up at too many levels.

> Thrust transfer during which different people can operate on each propeller.

> Thrust transfer that automatically disable gang.

> The steering rudder that gets reset when transferred.

> The steering taking the current state of the steering wheel when transferred.

> The manual mode that became the default mode, allowing the transfer of controls to empty stations.

The problem with touchscreens is not the touchscreen, it's the abstraction that makes possibles things that would make no sense with real controls. Why would, at any point, the current position of controls be different depending on the station you're looking at?

To me the main deal breaker with reST is titles that must be underlined with punctuation characters at least as long as the title.

That's very annoying to write, and some people even add overlining. We're entering the ascii art domain here and I don't have time for that.

It works out of the box with most browsers and like you said there are polyfills for older browsers. BTW the syntax with svg 2.0 is just href.

About the cross-origin issue, you mean it lacks something like a crossorigin attribute? That's only an issue if you plan to load svgs from other websites, I don't think it's a very common usecase. If you use them at multiples places in your website, you should probably have them served from your sever anyway, if not then I guess caching is less of an issue.

You can specify an svg file with the use tag like this: <use xlink:href="/your/icons.svg#whatever">

It pretty much solves the cache issue to me.

Ikea already understood that there is a market for this kind of goods. They sell a few hardwood furnitures which are not crazy expensive.

Yes it's now a available. Thank you !

Android app not available in my country, France.

A large part of the price in indeed related to offer vs demand but that's the basics for any market. Now it's funny because you also say "Estate agents charge more because people will pay it because anyone who can’t afford it goes homeless [...]". So it isn't just offer and demand isn't it?

When you think about it, even in areas like London the housing market is not liquid nor uniform enough for the offer vs demand model to apply. You don't rent/buy home like you buy strawberries.

In about 1 year there was no significant increase in demand and the supply stayed the same but everybody saw its rent increase.

Edit: Also we should not mix-things up, the housing market is very different in outliers like London compared to the more global market. Here we're in the context of those outliers (Paris, London, etc.)

No, price increase is mostly due to inflation trends. When there is an inflation trend the house market follows, for example in London, after the start of the war in Ukraine things like gas and gasoline price went up which created a legit price increase for products that depends on those. But we've also seen an increase in rent. And that's because estate agents knew that since there was an inflation trend people were expecting to pay more. So the whole market went up with no significant change in supply and demand.

With 2 children you'll need about 65sqm. Hopefully the nursery is cheap compared to other cities -cough London- but it adds up. Basically you need to be in the upper middle class for a decent life with children in Paris.

So it's a bug of the "automated remediation that makes things worse" family.

This system that checks for invalid values in the cache looks like a very bad idea in the first place as in my understanding it checks things beyond "is the cache up to date?".

Yep, I remember 8 years ago Intel trying to sell us their CPU solutions for AI. It was hard to make things work and in the end performance were not there. We were comparing against consumer gpu like the GTX 1080.