PhilipTrauner
Joined 10 years ago
Karma
545
Submissions
34
Member since
Jul 23
Recent submissions
Comment · 3 years ago
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.
Comment · 4 years ago
Seems that there are some code signing issues with the Apple silicon version. Intel one works fine though.
Comment · 4 years ago
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.
Comment · 4 years ago
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.
Comment · 4 years ago
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
Comment · 4 years ago
0_0 # Python >= 3.6 is required
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.
Comment · 4 years ago
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.
Comment · 4 years ago
Looks a bit like their cancelled take on Kanye West's stem player (https://imgur.com/a/ECehY1T), especially those faders on the front.
Comment · 4 years ago
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.
Comment · 5 years ago
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.
Comment · 5 years ago
> 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.
Comment · 5 years ago
> 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.
Comment · 5 years ago
> 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.
Comment · 5 years ago
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).