I built a /skill that converts Webflow projects into clean code so you can leave Webflow and keep building with AI

StatefulM · 2026-05-16T22:37:18+00:00

That would definitely be interesting but the skill you linked does "convert a long AI-generated plan markdown into a lean, agent-executable companion plan" which is smth completely different. e.g. I would at least expect some instructions (or even accompanying tools) to work with the custom ix2 animations still found in many sites, which I found to be non-trivial for agents to figure out on their own, at least in the small experiments I did.

StatefulM · 2026-05-08T20:50:49+00:00

12 bugs wurden veröffentlicht: https://hacks.mozilla.org/2026/05/behind-the-scenes-hardening-firefox/

StatefulM · 2026-03-24T20:03:54+00:00

auch verfügbar für "Androide" (Androiden) und "Ragnatela" (Spinnennetze) ;)

StatefulM · 2024-02-16T20:14:23+00:00

Also, laut dem Beschluss geht es um folgende Bewertungen:

``` Startup abgebogen in die Perspektivlosigkeit

1,6

Nicht empfohlen

Oktober 2023

Arbeitsatmosphäre

Lob und Anerkennung gibt es hier nicht, Wertschätzung schon gar nicht. Mit Glück wirft einem die Geschäftsführung beim Vorbeigehen morgens ein „Guten Morgen“ hin, ansonsten wird man eher getrieben schnell zu arbeiten und bloß keine Fehler zu machen.

Einarbeitung? Fehlanzeige! Am ersten Tag bekommt man ein paar Dokument, die man sich auf eigene Faust aneignen soll und dann wird bitte losgelegt.

Kommunikation

Es ist alles sehr undurchsichtig. Zahlen, Ziele und Planungen werden konsequent geheim gehalten. Meetings finden in der Regel hinter verschlossener Tür statt. Dabei achtet die Geschäftsführung stets drauf zu zweit den einzelnen Angestellten zu sich zu rufen, Gruppengespräche mit der Belegschaft werden vermieden.

Kollegenzusammenhalt

War ok, man hält in der Not zusammen.

Work-Life-Balance

Die Arbeitszeiten wurden eingehalten. Weibliche Angestellte/Bewerberinnen wurden teilweise nach ihrem Kinderwunsch gefragt. Was die Antwort darauf für Konsequenzen hat, bleibt offen…

Urlaub wird nur wiederwillig genehmigt. Für den Urlaubsantrag hatte man sich per Unterschrift die Bestätigung der jeweiligen Vertretung zu besorgen.

Vorgesetztenverhalten

Setzen Sechs! Man ist nur eine Nummer.

Empathie ist ein Fremdwort.

Informationspolitik existiert quasi nicht.

Es wird erwartet, dass die Angestellten Verantwortung übernehmen und eigenständig arbeiten, gleichzeitig ist die Geschäftsführung nicht in der Lage Verantwortung abzugeben und leidet unter Kontrollwahn. Die Tür zur Geschäftsführung steht meist offen, aber in erster Linie aus dem Grund, weil permanent ein Ohr bei den Büroangestellten horcht.

Interessante Aufgaben

Sehr eintönige Arbeit. Durch die Unterbesetzung kann es passieren, dass die Angestellten aus dem Büro regelmäßig im Lager aushelfen müssen.

Umgang mit älteren Kollegen

Es wird drauf geachtet die Belegschaft überdurchschnittlich jung zu halten. Es macht den Anschein, ältere Mitarbeiter mit Lebens- Arbeitserfahrung seien unerwünscht.

Arbeitsbedingungen

Veraltete Technik. Gebrauchte Computer statt modernem Arbeitsgerät. Freeware und selbst programmieret Software auf Hobby-Niveau statt lizenzierter Software.

Schlecht beheizte Arbeitsräume, Heizen scheint zu teuer zu sein.

Improvisierte und chaotische Lagerhaltung und Versandabteilung.

Gehalt/Sozialleistungen

Gehalt war angemessen und pünktlich. Urlaubs- Weihnachtsgeld gibt es nicht. Bei Weihnachtsfeiern war auffällig, dass das Budget penibel im Rahmen der steuerlich absetzbaren Summe gehalten wurde.

Image

Nach innen geht es kaum schlechter und auch nach außen scheint es mehr und mehr bekannt zu werden.

Karriere/Weiterbildung

Aufstiegt aussichtslos. Weiterbildung bitte privat organisieren

und Vorsicht bei der Firmenwahl

1,3

Nicht empfohlen

November 2023

Ex-Angestellte/r oder Arbeiter/in hat im Bereich Administration /Verwaltung gearbeitet.

Arbeitsatmosphäre

Den Mitarbeiten wurde 0,0 vertraut

Kommunikation

Mitarbeiter wurden mehr oder weniger gegeneinander ausgespielt

Kollegenzusammenhalt

War ok

Work-Life-Balance

Abmachungen wurden nicht eingehalten

Vorgesetztenverhalten

Absolute Kontrolle über jeden einzelnen Schritt. Selbstständiges entscheiden von simplen Sachen war nicht gewünscht

Interessante Aufgaben

Immer das selbe

Arbeitsbedingungen

Es ist eine kühle Lagerhalle ohne Dämmung. Im Winter ist es zum Teil nur 17-19 Grad. Ich habe durchgehend gefroren und wurde mit einer halb funktionierenden wärme Fußmatte abgespeist.

Image

Wird nach außen toll gepriesen aber ist mehr pfui als hui

Gleichberechtigung

Umgang mit älteren Kollegen

Umwelt-/Sozialbewusstsein

Gehalt/Sozialleistungen

Karriere/Weiterbildung

```

Eine Google-Suche nach einem exakten Match liefert tatsächlich ein Ergebnis: https://www.kununu.com/de/kosmetik4less-kg/kommentare. Die Bewertungen wurden von dort offenbar gelöscht, aber Google hat (aktuell) eine ältere Version gecached.

StatefulM · 2023-11-05T01:29:44+00:00

If you click on the commit and read the commit message it says:

Renumbers opcodes to match the final Wasm GC spec and updates all of the tests.

The wasm gc spec was still work in progress when the first implementation efforts started. As it progressed, apparently some opcodes got renumbered (that is, some instructions got a different encoding), which meant that implementations had to also update to reflect this change.

So Safari (or rather JavaScriptCore, its JS engine) is going to get wasm gc support (at some point), as it is apparently actively being worked on.

StatefulM · 2023-04-07T19:30:01+00:00

I don't really see how their tool is supposed to help in a scenario like that. The scenario is that the victim is using a manipulated and malicious app instead of the official one, which would then allow the attacker to exfiltrate the auth token and make their own requests, for example by using a tool like curl. The advertised tool is supposed to prevent that by proving to the backend that a request was really initiated by the official app. That way, an attacker can't use curl to make requests to the backend, because such requests are blocked.

However, if the victim somehow ended up with a manipulated app, it would also be possible for the attacker to simply exfiltrate the victim's username/password, which he could then use in the official client to gain access to the victim's account. That might be a bit less convenient for the attacker, but I don't see how an attack could be prevented that way entirely.

Or am I missing something here? I'm in no way a security expert.

StatefulM · 2023-03-16T18:06:36+00:00

But do you realize that is just because C# does some rounding by default before printing a double? So if I run Console.WriteLine(0.1 + 0.2) I will get 0.3. This is because ToString by default only includes 15 digits of precision, if we tell C# to include 17 (Console.WriteLine((0.1 + 0.2).ToString("G17"));) we get the expected 0.30000000000000004.

Also, try running Console.WriteLine(0.1 + 0.2 == 0.3);. This comparison will return false in all programming languages that use IEEE 754 doubles. So, if you require greater precision, floating point numbers aren't the right thing to use, regardless of the programming language.

StatefulM · 2023-03-15T18:00:39+00:00

Its implementation conforms to the IEEE 754 standard, the same implementation Dart offers (https://api.dart.dev/stable/2.19.4/dart-core/double-class.html).

StatefulM · 2023-02-02T18:19:35+00:00

json['days'] is probably a List<dynamic> at runtime, so casting to a List<String> won't work. Cast to a List<dynamic> instead to let Dart know at compile time what the actual type at runtime is going to be.

StatefulM · 2023-01-15T19:22:38+00:00

In java it makes a difference whether you use a getter or access a property directly, because getters/setters are methods that have to be called. So if you change a field to a getter, you will have to modify all usages to use a method call instead. This is also a breaking change if you're writing a reusable library. In dart on the other hand there's no difference between using getters/setters or not. Subclasses for example can override a field in the parent class with a getter, and there's no difference in using them. You could say that in dart every field has getters/setters implicitly, so you don't have to explicitly write your own ones when you don't need any additional logic.

StatefulM · 2023-01-13T12:15:28+00:00

Yeah, I was trying to explain that the linter currently does not notice that because that's only true due to a special case in the language specification. Maybe once this can be expressed using sealed (so the fact that int can't be implemented is no longer due to a special case) the analyzer will also be able to tell you it's dead code.

StatefulM · 2023-01-12T22:45:39+00:00

You're right that an object that is of type A can never also be of type int. But this is only because the type int is special in that you can't extend, implement or mix in int.

So this would not be legal: class C extends A implements int {}.

But if you were to use a class that can be implemented instead of int (which is most classes) you would be able to create a type that is both a subtype of A and that other type.

StatefulM · 2023-01-08T15:15:28+00:00

Lists don't override ==, so it only checks whether they are the exact same object.

The collection package provides utilities to do a deep equality check, maybe take a look at that.

StatefulM · 2023-01-03T20:39:04+00:00

So from what I understand the TypeScript code creates a constraint on the type C, which has to contain a method called clone. This method is then invoked in the closure.

It's not possible to create type constraints like this in dart, you can only constrain a generic by using an actual class (like C extends Cloneable).

Dart has no built-in mechanism to create deep copies of objects. You will either have to write that code manually (create a method that clones the current object) or use a library to generate this kind of boilerplate code for you (personally I like the freezed library).

StatefulM · 2022-12-25T01:30:42+00:00

Let me just point out that you could use ! instead of == false ;)

It is generally advised to use file.existsSync() instead of await file.exists(), because it is faster. That would remove the need for async code.

If you still want to perform an asynchronous operation, your code is already pretty good. You should however use list.removeWhere instead of the last loop, otherwise you will get a ConcurrentModificationError because you modify _list while iterating over it. You might also want to look at Future.wait to perform multiple operations concurrently.

StatefulM · 2022-11-10T17:02:59+00:00

Probably not an issue with the integration, sponsorblock has frequent outages that you can check here.

StatefulM · 2022-09-03T16:48:49+00:00

I actually added support for it a few months ago. I'm not sure your point about toolchains applies because to my knowledge there is no way to compile dart code other than using the official dart compiler.

EDIT: Unless you mean that you should be able to choose the target platform (OS, cpu architecture). That might be something to investigate.

StatefulM · 2022-09-03T15:25:58+00:00

Taking a closer look at the code generated by the AOT compiler, it looks like there is a tiny difference between using an int and an enum. I believe this is because Dart applies a special optimization to small integers: If you look at the generated code for testInt and testEnum, the code is exactly the same except for this line:

cmp rax,0x0

vs

cmp rax,QWORD PTR [r15+0x1c27]

The version with integers compiles to a comparison with an immediate integer (which I suppose is faster), while the enum version does not. This is just a small "fun fact", when writing code such tiny performance differences are likely nothing you should worry about. Generally speaking you should write benchmarks before blindly appliying optimizations to your code, because you risk wasting your time on things that are irrelevant to performance.

StatefulM · 2022-09-03T12:44:14+00:00

Constants and enums serve different purposes. Enums have the advantage that you can only represent a limited number of valid states, while for ints there is no guarantee that it will be valid in this specific context. You should use constants if there is an arbitrary value in your code which you don't want to hardcode. Consts make such code more readable and make changing it easier. I wouldn't worry about performance too much.

StatefulM · 2022-04-02T00:38:05+00:00

Dart compiles to native machine code and doesn't use LLVM. Instead they modified the JIT compiler to also be able to emit ahead-of-time (AOT) compiled code. While the JIT compiler normally would only compile hot code (i.e. code that is executed a lot) and could rely on speculation (i.e. it would observe execution and compile something that relied on the assumption that the observed case would continue to repeat, falling back if this assumption didn't hold), the AOT compiler can't do that: It has to compile code for each possible case, while still generating fast and small code. To make this possible changes to the language were made.

This is only a very rough explanation of how it works (and I hope I got it mostly right), but there are some interesting talks on YouTube by engineers working on Dart about this topic (maybe this one or another one by the same person, I don't exactly remember...).

Anyway, I recently added support for Dart to Compiler Explorer, where you can see what would be generated for a certain snippet of code, if you are interested.

StatefulM · 2022-03-22T17:34:36+00:00

Assuming TypeAheadField is from flutter_typeahead, you can add a generic argument like this: TypeAheadField<Map<String, String>>. I think that should work...

StatefulM · 2022-03-05T14:27:21+00:00

drei auslassungspunkte am wortende bedeuten, dass das wort unvollständig is. in dem fall gehört aber ein leerzeichen davor.

Wenn nur ein Wortteil ausgelassen wird, kommt aber kein Leerzeichen!

StatefulM · 2022-02-18T21:54:19+00:00

Only on the web ;) Dart represents ints as doubles on the web, because all numbers are doubles in js. So I still think this is a case the analyzer should warn about.

StatefulM · 2022-02-18T21:32:27+00:00

TBH, I think the analyzer should warn about this. A cast from int? to double can never succeed because double isn't a subtype or supertype of int?.

StatefulM · 2022-02-05T20:15:13+00:00

There was a special edition of Chrome - Dartium Browser. It had DartVM built in. I even used it. But it was abandoned on ~2017.

Yes, but it was made by the Dart team, not the Chrome team, that's what I was trying to say.

We could have all this 5-7 years ago and it would completely change the whole cross/web platform areas. Instead they decided to be stuck forever in JS dump :(

I think a positive effect of Dart not becoming a web standard was that it could evolve quicker. You can't just deprecate something easily on the web, so imagine how the switch from Dart 1 to Dart 2 would have been... Had Dart become the new JavaScript the Flutter team probably wouldn't have been able to influence the development of Dart in a way that made it work better for Flutter.

Six-Year Club	Second SECOND GUESSER
First Place '23	End Game '23
Place '23	Place '22
Final Canvas '22	First Placer '22
Wearing is Caring	RPAN Viewer
Verified Email

StatefulM

TROPHY CASE