This is super helpful. Not only does it help people understand how the system works but also this is invaluable for comparing offers. I always end up with a bunch of pencil scratch notes or if I’m really trying an excel sheet to compare offers.

I know sometimes we might only get one offer and you’re stoked about anything you get. However, I highly encourage everyone on the market to do what they can to have more than one offer. This has been the only way to truly have leverage while negotiating. I’ve also been surprised and joined a company that I thought was just going to give me leverage. Their offer was so much better and the team was a way better match for my skills and personality.

Feature Request: Add the ability to compare multiple offers and show a side by side comparison. Or maybe the ability to export to a CSV so people can do this themself.

Another feature request: add ability to compare their offer to offers on levels.fyi so they can know if they have room to negotiate.

Yeah, it really came from scratching my own itch in wanting a quicker/easier way to think through different companies offers. They always present them in slightly different ways

I really like the idea of a side by side comparison. I'll build that out next!

I imagine a virtual machine would be able to handle it just fine. Try VirtualBox

Unless you know something I don't, VirtualBox isn't qemu's CPU emulation - it's only virtualization for the current CPU. So, great if you want an alternative to Virtualization.framework but it's not going to run Windows 7 on Apple Silicon

And, even if it did run effectively under Rosetta, its management interface won't even let you select a non-arm64 guest: https://www.virtualbox.org/manual/topics/Introduction.html#h...

That's now how I use Netflix. I watch when I'm in the sauna and I've been on my phone long enough that I start to worry it will start overheating. Then I set up phone up outside the glass and Netflix gets my undivided attention. There are still so many great movies and tv shows on Netflix.

The name is John McStartup… it’s meant to be funny

I can confirm this personally as I had an infected version of Sub7. I thought it was so fun to mess with my parents with it until I realized I was now compromised.

https://en.wikipedia.org/wiki/Sub7

What I saw, as often as not, is that the skiddies using these tools would configure their installer/dropper and start sending it to victims, but accidentally run it on their own machine too. Meaning their own machine was now listening for control connections.

Which meant all a potential victim had to do was accept the file, not run it (renaming the extension was a good first step), and note the IP address of the skiddy who sent it to them. Inspect the file to see the port and password configured therein, run the control program, connect back to the origin IP with the given port and password, et voila.

I wonder how many of them thought their tool was backdoored, not realizing it was they who had compromised themselves.

Ah, the good ole' days of opening my friend(s) cd-rom drives. I was a wizard.

Seems like every installation had a backdoor password hardcoded too from that article.

I’m a recent convert to tailwind. I’m very comfortable with css and I was initially turned off on the huge horizontal lines I saw in tailwind projects.

However, more and more component libraries are based on tailwind so I decided to try some immersion therapy.

Here are the top things I enjoy that was not obvious to me:

1. The class names are css shortcuts. Using them save you a lot of time. This is probably obvious to anyone who’s seriously looked at tailwind but I didn’t see that browsing the docs. I just saw nightmarishly long lines.

2. The lines look longer when you are not familiar with the class names. I initially pulled all of my class names out into a string outside my markup and included similar to how I’m used to using emotioncss. This made tailwind tolerable for me at first. However after several days I started to feel less turned off by those lines. I think it’s because I could recognize them. I will still break down a line with something like clsx.

3. clsx helps so much vs trying to entirely rely on tailwind syntax. The docs don’t discourage this at all but for some reason I thought it wasn’t idiomatic tailwind at first.

4. My app has to support a very large number of themes. Tailwind has proven to be a very attractive way of solving this problem. CSS variables are cool but the long syntax of using them is helped a lot in tailwind.

5. Adding my own custom variants is so easy and made me feel like a power user with such a small learning curve.

All of this is just my two cents to guide anyone who is like me watching from the sideline and wondering why? Why would anyone ever want to tolerate those “disgusting long lines mixed into the html”. Neo, all I see is the lady in the red dress now

It's sort of like javascript devs ignoring typescript because they never felt like they needed it. But once you start using it, it's difficult to go back.

I was in never ts/tailwind gang for a few years until I tried them.

Giving me flashbacks to the AOL punters and proggies scene. <3

Tip for next time this happens: hold down the back button for a menu of your history. It can help get where you want faster. Although not sure it helps too much if you literally had to click 30 times

That or right click.

Sure, you can filter out some of the criticism as just haters. However, some of it might be deserved. It really depends on what the product is doing. Since Chat GPT is a very useful consumer facing product, any kind of chat bot built on top might not add a ton of value. Some companies are using an LLM such as GPT in very creative ways where you couldn’t get 80% of the value by just using the chat interface. You probably don’t see much hate in those cases.

This is very cool! I love seeing tooling targeting inference. I feel like stable diffusion and LLAMA have to be the primary use cases for these types of services. DALL-E is super lacking and GPT does actually start to get pretty expensive once you are using it in production.