This is pretty shady. The $17B figure is much less impressive when a huge chunk of it is hinged on competitors choosing to hurt their business.
2,950 karma · joined October 18, 2012
Somewhat obsessed with new tech and startups.
http://joewegner.com hn@joewegner.com
This is pretty shady. The $17B figure is much less impressive when a huge chunk of it is hinged on competitors choosing to hurt their business.
The provided software is clunky, and the plugins suck. I’ve been building an app for designing stickers, and what I really want is to either be able to drive the Cameo from the app directly, or output a design file in a format that can be loaded straight into the software to start cutting.
The thing I’m stuck on is… how do people reverse engineer these devices protocols, without fear of bricking the device? My understanding is that reverse engineering like this is a lot of “try shit and see if it works”. It seems to me that a few wrong commands could get the cameo in some irrecoverable state. Obviously that’s not a risk I’m willing to take on a machine I use very regularly.
- Before cell phones, we were also in an age of far less mass violence in American schools. I completely empathize with parents wanting their kids to have an emergency contact device, given the relative increase in violence at schools.
- There is a long history of kids being abused, sexually or otherwise, by authority figures in their school. Having a lifeline like a quick text to a parent can easily be the escape hatch from a predator convincing a kid to do something unsafe.
This doesn't seem applicable in most contexts. Yes, when I'm coding for fun or purely for learning the finished product is less relevant... but I'd guess the vast majority of code that is written is for a business that _only_ cares about the product. Code is an implementation detail.
If (and this is a _big_ if) AI-based coding can increase developer velocity even as little as 50%, no sane business is going to let their engineers ignore it just because it's not as fun as artisanal code.
It’s been a common mantra - at least in my bubble of technologists - that a good majority of the software engineering skill set is knowing how to search well. Knowing when search is the right tool, how to format a query, how to peruse the results and find the useful ones, what results indicate a bad query you should adjust… these all sort of become second nature the longer you’ve been using Search, but I also have noticed them as an obvious difference between people that are tech-adept vs not.
LLMs seems to have a very similar usability pattern. They’re not always the right tool, and are crippled by bad prompting. Even with good prompting, you need to know how to notice good results vs bad, how to cherry-pick and refine the useful bits, and have a sense for when to start over with a fresh prompt. And none of this is really _hard_ - just like Search, none of us need to go take a course on prompting - IMO folks jusr need to engage with LLMs as a non-perfect tool they are learning how to wield.
The fact that we have to learn a tool doesn’t make it a bad one. The fact that a tool doesn’t always get it 100% on the first try doesn’t make it useless. I strip a lot of screws with my screwdriver, but I don’t blame the screwdriver.
Not that that takes away from the article at all. This project has many merits, and although cost may not be one of them, it’s still interesting!
I know nearly nothing about rocketry, so ELI5 (or give me a wikipedia link!)... anyone know what those floaters are? Is it some byproduct of the fuel? An artifact of the cameras? An illusion coming through the haze of the burning rocket?
OpenAI is charging a _really_ high monthly fee for ChatGPT, and it’s quite popular. It’s very limited - there’s no way the cost incurred for usage is near that. Obviously their costs include the R&D that has already happened, but I still think it’s priced way over that.
Drug manufacturers are famously making money hand over fist. Patients aren’t their customers. Insurance companies are. They are surely gouging insurance companies to their fullest capacity.
While it is correct that marriage has traditionally been a union of people of two different sexes, I think the root of the issue is that is not how many people perceive the tradition in reality. I, along with many people, view marriage as a union between _two people_ - regardless of gender. The fact that marriage has mostly always been across sexes is a side effect of centuries of homophobia/heteronormativity.
So saying that marriage is meant for a man and a woman does not compute for me. Trying to enforce that is _taking away_ from my concept of marriage.
Or maybe this is another VC-backed sale price :)
> the server-rendered HTML will always default to light mode. This creates a flicker for night owls
You might consider switching this - render the dark-mode version by default, and have the flicker be from dark-to-light. For users operating mostly in dark mode, a bright flash of white can be painful. The same is not true for users operating in light mode - they will barely notice a moment of dark.
I will turn it off on the 12th, and we will just suffer without it until we all quit and the sub dies. Oh well.
Using a CLI-based tool is inaccessible for most people... but building a GUI around this would be very easy. I'm too lazy to google it, but I would bet someone already has a GUI, or is working on one.
12GB of VRAM may not be accessible on most computers, but there's nothing innovative about offloading that task to an EC2 instance. It just requires an opportunistic developer to tie the pieces together.
I would be monumentally surprised if Figma/Canva/InVision/Adobe are not already working on this.