justusw

So Django did not fit the author’s use case of implementing endless scrolling? How is Next better at this? Are there use cases where one could be suited more than the other, before we completely start writing off everything else?

Links to further reading would be appreciated!

Is there a service that supports SSO?

I was told I value financial independence, but doesn’t that apply to pretty much everyone? Seems like generic horoscope language overall. But definitely provocative and made me want to write a comment to complain, ironic. +1

What a great book! It was my introduction to 32-bit assembly on Linux. Learning AT&T syntax has both its advantages as well as drawbacks. I've noticed a lot of GNU code uses it, whereas reverse engineering literature loves Intel syntax, which is an interesting cultural difference.

If you bundle it and release a paid for application on the App Store, I would totally buy it and even roll it out to my staff. The magic of the App Store allows you to do company wide roll-outs quite easily.

As far as I understand, Gecko and Blink are completely separate, and if we were to put things together with slashes, Chrome/Edge/Opera (Blink) and then Safari (WebKit) share the same lineage (and even Konqueror!). Firefox/Gecko come from a very different direction. To call out investors behind commercial project fails to acknowledge the rich OSS history behind the browser engines. By no means I intend to disregard the tremendous influence Google exerts on web standards with their browser monopoly, but putting it all in the same bin does not help the issue anymore so.

Accusations are easy and can be made in seconds, a defense takes care and thought. See politicians lying impromptu, and journalists spending hours on debunking.

That explains why my former employee had signs of a crossed through Bento in their bathrooms (here in Tokyo). The sign also said to refrain from napping or using your phone in the restroom. How exactly they found out what people do in the stalls remains a mystery.

According to my former coworkers, hiding away in bathrooms is endemic in ブラック companies. The company I worked for was a game company, so they also had nap rooms for the inevitable crunch time.

If you are looking for a job in Tokyo, watch out for nap rooms and bathroom signs that says no food.

This is such a cool idea and execution. I also like the DIY approach to patching MPC BE yourself, which shows how far OSS can take you.

I wonder, when applying a linear transformation like in the shader described, will the total available color space decrease? Simply put, if a one-dimensional color value on the arbitrary scale between 1 and 100 needs to be decreased by 20 for correction, the resulting maximum will be 80. Does that mean the total available color values will be less?

I hear you, the last thing I want to feel is dread when implementing something. But recently my priorities have shifted a lot with regards to using the fancy, the new and the shiny. Sometimes I just want to end the day with getting something done and going home with the feeling of satisfaction and having achieved something tangible. Again, context matters with these things.

And with regards to employee retention, I would rather bet big on benefits (paid time off, parental leave, etc.), reasonable working hours (4 days per week), achievable goals, great communication, democracy and good team cohesion. I have a feeling this works for a lot of people. If a language is the only thing that makes you stay, by all means find a place that truly makes you happy in that regard. All I am saying is that there are a lot more variables to worker satisfaction.

That's an interesting point. Do you think your friend was able to deliver at such speed because of the familiarity with Erlang? Or was it so, that even with a lack of familiarity, the other advantages of the language were overwhelming? Also, may I ask what kind of application was being developed?

I also wonder how we can define popularity better. Does that mean industry acceptance, number of GitHub repositories, number of StackOverflow questions, number of libraries, developer satisfaction surveys, etc. If you choose different metrics here, different languages and frameworks will appear popular. Svelte for example seems to be on top of some developer satisfaction surveys, but React is still one of the number one choices for frontends. C is the industry standard for embedded, but developers often do not enjoy programming in it.

Ruby on Rails used to be one of the most popular ways of implementing MVC applications in the server. Has Ruby been hit by a similar fate?

I agree. For most CRUD applications, developers should mostly integrating off-the-shelf components, and not constantly be reinventing the wheel. The reason for that being, that customer value (and satisfaction) can be attained by delivering a usable product, and that is what pays the bills at the end of the day. Whether that product is implemented in Python or Elixir is often not visible.

On the other hand, if the task at hand requires a novel approach and using tools that are less frequently used, then that will also be justifiable. Are you developing something that only makes sense to run on the BEAM virtual machine? Go ahead and work with Erlang or Elixir.

Now a third category is programming for enjoyment. In that case you don't work with the constraints of profitability, and you can just have fun. And don't worry too much about Beating the Averages (http://www.paulgraham.com/avg.html)

Honestly, I just send a request and see if I get a 403/401 or not. With DRF you get an additional "auth credentials required" error JSON object back, so you can just evaluate that client side. Since I use fetch for my current project, I just need to check the response.

I agree, Tailwind seems to be out of scope here for comparison. One is about server architecture, the other one is about how to write CSS. Both have a completely different impact (JWT as a footgun vs. Tailwind improving/worsening developer comfort)

Proving the absence of a 0 day for whatever your solution you are using is always going to be difficult. But dwelling in thoughts like this is close to crossing the border to FUD territory. And who says there isn't a 0 day for Firebase auth?

We can put our faith in systems that have been hardened over the years and are easy and reliable to implement. And email + hashed/salted password belongs to them. And by that, I specifically mean using a library that takes over the hash/salting part for you. For me, not rolling your own crypto not only means not implementing your own hash algorithm, but also staying off-the-shelf with the code that calls said cryptographic functions.

I also like to stay conservative with regards to session cookies vs. JWTs. One has been around for more than 2 decades, is well understood, and has some really solid cross-browser security measures behind it (HttpOnly, Secure Cookie, etc.)

I personally like using the Django contrib auth library for this purpose.

Can you explain what’s suspicious?

I assume this is using a lot of soft synths and samples? Whatever they are, they sound really cheap. I hope I don't back myself into some Luddite corner here and this later turns out to be really impressive, like we are seeing in the image generation space. But given that we are living in a market of overabundance of stock photos, royalty free music, etc., I am sure that this is not endangering anything anytime soon.

And while comparing it to image generation, with Stable Diffusion and other models, a human has to be in the loop in order to generate the prompts, so we can't entirely replace them here either. How about an AI music generator that creates phrases, rhythms or sounds/VST presets based on a prompt for me?

If an average person can choose between listening to this, or listening to a musician that they have a personal connection to on their favorite streaming service, I wonder which one will be picked most of the time?

I agree, pathlib is really powerful, and I can see myself using it for new developments.

May I then assume that Refurb is better suited to work on new code? To get back to open(), I don’t know if I would want to go through my company’s legacy code (which runs on Python 3.10) and start replacing battle-tested code everywhere. Same would go for tuple literals over lists in certain circumstances.

I think this will go really well with choosing an „acceptable“ subset of Python for your project, similar to how some companies choose a subset of C++ and then stick with that throughout a project.

I understand that some of these suggestions have been made possible by recent changes to Python 3. But how do I know whether a specific change suggestion will genuinely improve my codebase vs. just confuse Python developers who are used to seeing things implemented a certain way (e.g., Path lib vs open() )? It would certainly make sense to add more information on the tradeoffs and what long term benefits writing it in a certain way will be.

This is just my personal opinion and after evaluating it from a compatibility angle I found that Azure AD is suitable. We are using it with Nextcloud, Apple Business Manager, Tailscale and Figma. U2F is not well supported, but OTP works well (with yubico auth as well of course.

Are you talking about customer facing SSO?

We just recently have upgraded to Figma enterprise (which is an annual contract) in order to get SSO. It is definitely reassuring to hear that our data won’t be trapped forever if Figma goes the way of the Creative Cloud. I hope that either Penpot will close the gap, or that Sketch will improve their in-browser game.

    W3.CSS is free to use. No license is necessary.

Does that not constitute a license?

Am I right to assume that Prettier runs single-threaded? I was never able to find an option to parallelize (and I assume it is paralellizable). Being able to speed up Prettier would improve my workflow by a lot.

UG also stands for unlautere Geschäfte, dishonest dealings ;)

On a similar note, Azure only supports U2F with yubikey on select Windows / macOS environments, but Firefox ESR on Debian is not supported at all. Every other service I use supports U2F just fine on Linux, but Microsoft wants Linux users to live slightly more insecure.

Are those two things in the same field?

Bringing change by strengthening economic and cultural ties has been tried for a few decades now with mixed results. Be that the United States–China Relations Act of 2000 during the Clinton administration, or Angela Merkel cozying up with Russia during her chancellorship. In one case, it didn't keep China from abusing its Uyghur citizens, in the other case, it didn't keep Russia from invading Ukraine.