Personally, I'd love to see you optimize for people who start and iterate upon an app from a mobile device and preview/use the app on the same device. Since the messages are just English text, the extra presses to type curly/square braces don't constrain you on mobile. Sometimes I get writer's block at my computer in a way that I don't get on my phone.
In particular, I'd hide/disable the sign-in-with-Google pop-up on phone-size screens (it takes a third of the screen for me), and make sure that CSS/styling makes everything fit on the code and preview screens on a phone, even in mWeb.
My impression is that the "indistinguishable from placebo" is only in reference to a study on people with Sciatica, but that a different study did show a statistically-significant effect on post-surgical pain.
$465 USD for a 15-day supply definitely pricey -- but options for people who weren't well-served by Purdue Pharma / OxyContin seem good, especially if the mechanism of action is different.
I drove a leased PHEV in California from 2021 to 2024. Driving on electricity was more expensive!
Typically charged at L2 chargers at a retail rate of $0.39/kWh (admittedly during dinner peak after work -- off-peak was lower). The 17 kWh battery gave 40 miles of highway driving, for 16.575 cents/mi.
Gas during the same period peaked at $6.749/gal, although I went out of my way to fill up at Costco Gas and saw prices as low as $3.999/gal - weighted average over that three year period was $4.896/gal. The 7 gallon tank gave another 300 miles of highway driving, getting 9.331 cents/mi to 15.748 cents/mi.
At the same gas prices, a comparable gas-only car getting 29.1 MPG would be 13.8-23.2 cents/mi in gas costs.
I'd expect big companies to use Markmonitor to handle this problem -- basically, they _also_ register all of the one-edit-distance away typos that they can.
According to Wikipedia, Akamai is one of Markmonitor's customers, so it is surprising that this wasn't already registered by them.
I've found that Markmonitor is generally signed up for "public" address like akamai.com but rarely signed up for service domains since "who is going to screw up the service domain?"
In my experience, the main drawback is cognitive complexity: there are not one but four different implementations of map and set provided, each with slightly different memory and compatibility tradeoffs, and using the wrong one may break existing code that depends on (for example) stability of pointers to elements or iterators during set mutation.
A "normal person" is a Starbucks barista making $38k/year (roughly 2000 hours at $19/hour).
That person doesn't spend 3 days' wages for "mainline kernel drivers" -- either they buy the iPhone because it's a status symbol, or they use the Android OS that shipped with the device for three years until the screen is cracked and the battery stops charging. To them security patches are just an inconvenience.
I don't think "if only people had the right information they'd spend money on the right things" is the right thesis -- I think it's more "why is everyone so poor? how do we make it so that more people can afford our wares?"
My impression (citation needed) is that globally folks have been worse off the last few years and so the median Android device spec was actually going down.
> either they buy the iPhone because it's a status symbol, or they use the Android OS that shipped with the device for three years until the screen is cracked and the battery stops charging.
That's also exactly the point. Why is it hard or expensive to repair the device? Would they have purposely chosen a phone they have to throw away like trash and then pay more than a hundred dollars for a new one if they could get one where a new battery is $15 and can be replaced like they do the batteries in their TV remote?
> My impression (citation needed) is that globally folks have been worse off the last few years and so the median Android device spec was actually going down.
Or people have realized that they only use their phone for maps and texting and they don't need a flagship if they're just going to throw it in the trash in two years anyway.
> the median Android device spec was actually going down.
What is so great about the top end phone that I should get one? They all have cameras (plural) with more pixels than I can see. They all have a fair amount of storage.... Sure the top end models have more of everything, but is there anything that I as a user would notice?
I was one of the first to have an Android back when the G1 came out - the hardware was lacking, but any phone from 4 years later was good enough (except none had a slide out keyboard that was so much nicer than touch screens)
Looks like it does not allow new channels for 6 GHz Wi-Fi. 802.11be (Wi-Fi 7) already covers full range of FCC's allowed frequency range. IEEE committee may add new channels in 802.11bn (expected to be ratified around 2028, and commercial name will be Wi-Fi 8) but it also looks like a low probably, considering both 802.11ax (Wi-Fi 6/ Wi-Fi 6e) and 802.11be (Wi-Fi 7) mostly focuses on reducing the interference between different networks by reducing the collision, instead of widening the spectrum (BSS coloring, Flexible Channel Utilization etc.)
1) VLP: can now happen in 1200 MHz (5925 MHz to 7125 MHz); previously it was only 850 MHz.
Very Low Power: 25 mW (14 dBm) power.. with -5 dBm/MHz PSD, indoor and outdoor usage.
Think of short range use-cases like smartphone to laptop or smartphone to earbuds/ARVR.
2) LPI: already allowed in full 1200 MHz
Low Power Indoor: 1W (30 dBm) power with 5 dBm/MHz PSD (clients are 6 dB lower); only indoor usage.
Think of your home router.
3) SP: allowed in 850 MHz; no plan to expand AFAIK
Standard Power: 4W (36 dBm) power with 23 dBm/MHz PSD (clients are 6 dB lower); indoor or outdoor usage.
Requires Aautomated Frequency Coordination; send your location to cloud, cloud tell you which channels area available.
Think of enterprise or high power routers; outdoor point to point links (WISP)
So, this new regulation is only for VLP and will result in more (especially 320 MHz) channels. No change to the most common usage of Wi-Fi (Router to Laptop/PC).
I'd expect a very different experience with Devin vs the IDE-forks -- it provides status updates in Slack, runs CI, and when it's done it puts up a pull request in GitHub.
Thanks, but that comparison is for old models, a different, non-shipped version of Devin called “Devin-base”, and doesn’t include Claude.
Slack integration, automatically pushing to CI, etc., are relatively low-value compared to the questions of “does it write better code than alternatives?”, “can I depend on it to solve hard problems?”, “will I still need a Cursor and/or ChatGPT Pro subscription to debug Devin’s mistakes?”
In particular, I'd hide/disable the sign-in-with-Google pop-up on phone-size screens (it takes a third of the screen for me), and make sure that CSS/styling makes everything fit on the code and preview screens on a phone, even in mWeb.
reply