PhilipTrauner

Now you got me curious: can you get Dashcode to run on modern macOS or does it only work on Snow Leopard? Never got to experience it back in the day and would love to try it out.

Seems that there are some code signing issues with the Apple silicon version. Intel one works fine though.

I agree with the need for a standardized development setup (be it local or in the cloud) but violently disagree with eliminating development setup diversity.

Curious engineers with oddball configurations greatly contribute to the overall health of a codebase. Forcing these folks to use a standardized configuration is a missed opportunity at best, and disgruntling at worst.

You can already do that right now (even Vulkan should work fine through MoltenVk), although accessibility will be poor when compared with Apple's offering unless significant effort is invested.

Can't help but feel that this approach might not be that cursed after all, seeing how you actually went through the effort of automatically testing all of these.

Nothing beats this guy though: 0_0

  0_0  # Python >= 3.6 is required

(https://github.com/jwilk/abmagick/blob/8959fe7c390283d095e42...)

Highly cursed, yet wildly creative way of asserting the language version.

Support for underscores in numeric literals landed in 3.6 (PEP-515), < 3.6 chokes on the underscore and raises a syntax error instead.

UIFeedbackGenerator (https://developer.apple.com/documentation/uikit/uifeedbackge...) has been around for a while, but it’s not exactly capable of "positional" feedback. Still, vibrating in response to actions such as rearranging list entries or drag interactions that require a certain distance threshold to be passed can feel quite satisfying.

Looks a bit like their cancelled take on Kanye West's stem player (https://imgur.com/a/ECehY1T), especially those faders on the front.

Neat, but I seriously hope that it doesn’t become popular enough to force Spotify to combat client reimplementations such as librespot, which this is based on.

The release notes don't include release dates, but if the Twitter account registration date is to be trusted, Typora has been around since late 2014.

A one time 15$ purchase is a steal for all the value I got out of the beta versions over the years.

Even Sublime Text 3's monumentally long beta period appears brief when compared with Typora's.

> Tailwind UI’s Figma file has the highest level of quality I’ve ever seen in an external Figma file

This cannot be overstated. The included Figma file alone is arguably worth Tailwind UI's asking price.

> As long as their database in docker is being incrementally updated (using the same migration scripts as on production which only apply new ones) is this hit only when spinning up a clean docker image?

Yes, but being able to quickly return to a known-good state by trashing the database is still useful because getting migrations right without testing them is hard.

Using named volumes helps because they don't need to be bridged through to the host filesystem.

> This all runs as a pre-commit hook as well.

Keep in mind that this might become problematic for folks that are running Postgres inside Docker on macOS or Windows, as IO performance is quite poor.

I put together a up / down migration validation system a while ago (start up two databases, apply all-1 up migrations on A and all up migrations + final down migration on B) for a pretty sizable schema.

Folks that were using Docker had to wait upwards of two minutes, while natively installed Postgres would finish in under 10sec.

There's a similar project (https://github.com/erik/squabble), that uses a portable version of Postgres' SQL parser to spit out an AST, which lints can consequently traverse. This approach alleviates the need for bringing up a Postgres cluster to lint the schema. I'd be curious to know if there's something to be gained by depending on a running database instance (especially because it complicates CI).

Quoting the issue that the creator opened on the original repo (https://github.com/SweetIQ/schemats/issues/127):

> I figured having one that upgrades all the dependencies and uses some of the newer JS features would be a nice win.

Is this "fork" also going to address all the other Postgres-related issues of the original?

27.5kg strikes me as really heavy considering most other electric scooters come in at around 15kg.

Since I've started using black as a pre-commit hook and an editor extension, I have noticed that I tend to use inline-if expressions and lists comprehensions much more liberally, because I do not have to worry about formatting all the time. Begone temporary variables!

If what I wrote came across that way I'm really sorry. My intention was to cover the state of Linux in general on the XPS 15, an "operating system" choice that Dell does not endorse. I felt that my experience with the machine might somehow be relevant to potential buyers that want to replace their current MacBook with non Apple hardware, who also aren't willing to use Windows. The distribution the I mentioned in the post is largely irrelevant to the premise I set out to cover, as Debian testing can basically be described as a very bleeding-edge Debian variant and everything I stated would still be relevant for Arch or any other distro. I still stand behind that original premise, but it seems that I somewhat screwed up the delivery.

Functionality wise it doesn't differ at all, and it shouldn't because youtube-dl is a good media scraper. Where youtube-dl falls flat (in my opinion) is maintainability, size, external dependencies and its usage as a library. Offliberate uses Offliberty as its backend and does not contain any extraction code for specific sites whatsoever and thus remains very small (the command line interface is in fact larger than the resolver). youtube-dl currently has 1436 open issues as well as 184 pull requests on GitHub. Lots of their unit-tests also fail and take ages to complete. Offliberate uses no external dependencies other than requests and does not rely on other command line utilities such as ffmpeg for content stitching. The last difference is the emphasis on usage as a library. The CLI logic is separate from the actual resolver which can work asynchronously as well as synchronous.

Yep, you can tell by the way the helicopter sounds and the walking animation for spiderman. The motion blur also looks very similar. The terrible looking ENB mod makes it difficult to notice, tough.

Removed that paragraph from the readme. While there indeed are projects that have done this before (Django) setuptools is definitely not a config utility and does not define variables on a module wide level.