HN user

l3s2d

151 karma
Posts1
Comments51
View on HN

It wasn't clear from your comment if you're aware of this, but Flutter hot-reload works from the command line too! I do all my Flutter development in 3 windows (vim, `flutter run` shell, android emulator).

I've found that IDEs work well when you're working within a single language or framework, but are clunky for multi-language projects. It's easier for me to have 4 terminals open (2 for vim, 2 for execution) than two different language-aware IDEs. With the IDEs, I need to pay attention to which IDE I'm in since they have different shortcuts and UIs.

I think OIDC should be the default authentication for services like this. It is the newest, and simplest, of the three. Any sort of integration with existing SAML or LDAP can be done via a bridge. Keycloak supports this, I believe.

General observation, not necessarily related to this project:

It's rather unfortunate that federated identity is always an afterthought instead of the default. Every new project could have been using OpenID Connect instead of rolling their own authentication. I really wish web frameworks pushed for this.

I suppose some of the blame lies with the identity providers. So many of them use a custom OAuth protocol instead of OIDC, which shifts the burden to the developers. Adding a new IdP should be as simple as adding a new trusted URL, instead it's often integrating a new SDK.

This is an interesting solution to a problem I hadn't given much thought to in the past.

On the one hand, it's demoralizing that we've reached this point where misinformation spreads at the same rate as good information. On the other, it does seem like a decent way to expose predatory journals.

Could this method be extended to other fields?

Absolutely.

As much as I dislike Apple, their ecosystem works for them and their users. Unfortunately the general public isn't aware of the restrictions imposed on them until it matters, like when their screen is broken and they can't pay $$$ for a first party repair.

We need regulation coining and enforcing accurate terminology for the relationship between vendors like Apple and Tesla, and their users. It's not ownership. If I can't run whatever software I want on hardware that I paid for, I don't own the hardware.

Can you imagine if your mattress didn't work with third party bed frames? Or pillows?

Yes, I believe there are several flavors of source-available license that attempt to meet this requirement.

Code released under such a license would not qualify as open source, but it could allow for individuals to maintain the software themselves. A license like the BSL could even be structured to transition the code to open source after some amount of time.

I've been using the v1 Bluetooth keyboard as my daily driver for almost 2 years. Solid construction and very portable, but lately I've been plagued with frequent disconnects and input lag. Has anyone had experience with the v2 on Linux?