raydenvm

Apple is simply repeating Samsung, Google and the other companies with their Duo model. Nothing revolutional, nothing "one more thing amazing". Another heavy and clunky foldable phone. I bet that folding durability will disappoint the users after all.

Yeah, it makes you wonder how much computing power the industry has wasted over the years on tools that nobody questioned because "that's just how long builds take." We planned our work around it, joked about creating breaks, and built entire caching layers to work around it.

Kudos to the Vite maintainers!

I was also thinking between these two. Still see the diffrence: I guess "critical path" is single, bottlenecks are multiple.

Awesome stuff! It would also be nice to add Opus Spicatum method when tiles are set at angles to form a “herringbone” zigzag pattern. It should be quite easy to implement: https://en.wikipedia.org/wiki/Opus_spicatum

Excuse me, I can't help but cite this one wonderful song:

"When everything's made to be broken, I just want you to know who I am" (c) Iris by Goo Goo Dolls

I feel it touches on something deep that has to do with the current state of the tech world.

Are there any known commercial use cases?

I suppose that switching to Brave will be one of the best solutions after all. They have already comment this in June: https://brave.com/blog/brave-shields-manifest-v3

I'd like to know how you intend to handle the infrastructure costs of providing this for free.

Also, how do you see the future of disposable email services as companies get better at detecting them?

He may easily cancel it in two weeks. With Trump, it's almost unpredictable how things will go.

Thanks a lot for sharing! A great food for thoughts. And yeah, I definitely don't want to build a custom solution - it should be max reliable and fast enough.

Same story with me. It says for both Workspace and Personal accounts that they are Workspace.

Have you managed to overcome that?

You can also consider self-publishing taking into account the modern AI capabilities. Why don't try it, including Korean language, maybe with the final review by a human?

Here is the experience of Jurgen Appelo with his new book who decided to self-publish it: https://jurgenappelo.com/blogs/news/just-because-you-can

Prior to this one, Jurgen had written around 8 books using the traditional publishing approach.

Funnily enough, a lot in Liquid Glass is inspired by older design systems from Microsoft : Fluent Design (Win 11) and Windows Aero (Win 7). It shows how real tough it is now to come with something really new these days in design.

Consider changing the name. Destiny is a strong gaming brand, but it's also generic. It will be extremely difficult to build a new brand and stand out.

It might be better to choose a name that works well with Wormhole. Check Google and the App Store to make sure there is no powerful brand with the new name.

Thanks for sharing your experience!

Actually, it's a small victory for Rust fans :)

Looks nice. It's just super insecure to use browser extensions which is very limiting for distribution

You mean non-commercial open source, right? Well, perhaps... I can't say with certainty because I was never involved in one.

At some point, I also learned that code quality does not really matter. Product quality has an impact, but not code quality. With AI, it will likely matter even less because code quantity dramatically increases at the expense of quality.

How much time/money would you save then?

1. What about the concept of minimum loveable products (MLP) versus minimum viable products (MVP)? They say go for MLP and that with MVP, your chances are much lower due to the excessive product and information noise.

Have you ever felt tempted to drop your main job because your side project was growing?

File names were limited to just 14 characters - UNIX file system called as "Version 6 filesystem". Directory entries, for instance, consisted of: - 2 bytes for the inode number - 14 bytes for the filename

After that, the next file systems went up to 255 characters.

The path from cloud-first to self-hosted is common. Self-hosted options often enable enterprise deals that were previously impossible due to compliance requirements. However, the development overhead is significant. The key question is whether your addressable market size justifies the additional complexity.

The self-hosted pricing omes with a significant premium (often 2-3x cloud pricing) plus professional services revenue for implementation and support. Many companies find the professional services component becomes unexpectedly lucrative but resource-intensive.

I live in Ukraine. So I donate to lots of funds like United24 and Come Back Alive Foundation. I believe it helps stop the war and the aggressor. Thousands die every day...

Beautiful one! I have been a fan of hotkeys since childhood. How did you decide to choose "Cmd + C" twice? Were there other competing options that might be quicker and not in conflict with other hotkeys?

Which is not scalable, right?

When people want a heavyweight stuff around forms including all the integrations with Zapier, Google docs, Notion, Airtable, etc, they go Tally or Typeform for $25 per/month. I see Forms.md as a an overpriced and less capable solution. For that kind of value, even with everything you enumerated, I can't expect users paying $99 for each form website. When I consult startups, I repeat guys: fast-growing AI code generators and editors will push you out of the market if you don't come strong differentiated value with free and very low-priced tagged packages (< $10).

It's partly different. Users focus on solutions, not products. The pricing model must be prepared for that. $99 per site is too expensive in a market with so many free solutions. $19 may be the possible maximum, or even less

This reminds me of the UML/RUP era from the early 2000s.... Is that an attempt to revive or even resurrect UML diagrams and Rational Unified Process blending it with AI? I would bet it's all dead forever. I'm skeptical about diagram-driven development making a comeback. In my experience, developers today prefer more agile, code-first approaches because requirements change rapidly and maintaining diagram-code synchronization is an unbearable challenge.