I don't know if it's just me (checked in Firefox and Chrome), but the black text on the red buttons is really hard to read. I'd suggest using white, unless you had some reason to use black.
During that time, the web was mostly brochure websites. No revenue was generated from these sites as they were purely informational.
"Web 2.0" was born during this time (maybe a little later) and introduced a paradigm shift where the Internet was becoming more commercial. It took some time for things like merchant accounts to run credit cards to become available for Internet usage, which was huge since fraud was a major consideration with Internet shopping. There was also none, or very few, SaaS eCommerce platforms like Shopify, so eCommerce was mostly a roll-your-own or use a new open source eCommerce platform that was in its infancy. It wasn't until the mid 2000s that popular self hosted platforms like OpenCart, Magento, PrestaShop, WooCommerc, etc, were available and mostly feature complete for most customers needs back then.
Torvalds is not a UX person. If the creator is indifferent, you get a slew of commands and flags that map to the data structures and idiosyncrasies of the creator, rather than anything presenting a cohesive API to the outside world.
Motorola does a pretty good job. Their "bloatware" is mostly the Moto app, which provides really handy and reliable gestures like a double "chop" to toggle flashlight, twisting the phone a few times to enable the camera, three-finger screenshot trigger, etc.
Their phones are really solid but they do lag on OS updates, and their cameras are never good.
Came here to say pretty much exactly that. I've been on a series of moto G phones, from the 5 to my current G83. Good value, the moto app actually adds functionality without being a drag (or even mandatory to use).
Cameras are always sub-par (partner has pixels, and I'm light years behind), although the latest is the least bad in comparison with her current phone.
Current one has survived most of me building a home extension with little damage...previous one developed an intermittent screen touch issue, but only after I dropped it 12 feet onto a concrete floor,so I can't complain on reliability either.
Just want to mention that the moto camera is made FAR worse by the software.
E.g. video on my moto would always be blurry due to bad de-noising settings used by stock software. mcpro24fps allowed me to take dramatically better videos. The difference was HUGE.
Same with photos. Custom gcam roms, after a long time of trying different ones and tweaking, gave me dramatically higher quality photos. Again, night and day difference.
So the hardware is fine; they shoot themselves in the foot with the software.
Can you provide more details about your current setup? Firmware versions, diffs, settings, etc? Maybe tutorials you used to get your camera into good shape?
Tried loads of GCam versions, the one that worked best was LMC8.4R8. Camera and Night Sight work amazingly well, and all 3 cameras are supported.
For videos however I had to use mcpro24fps. I don't recall the details now, but basically videos from stock camera app looked far blurrier than the photos, suggesting a software issue. It turned out to be some denoising feature that is on by default with no option to switch it off. You can also try it out by installing Open Camera, enabling Camera2 API and disabling Noise Reduction in Processing settings.
Unfortunately, I have not found a way to record slow-motion (high-fps) videos without the noise-reduction blur.
> but only after I dropped it 12 feet onto a concrete floor
My brain went right to old Nokia phones and I thinking "Thank fuck it was a Motorola, back in the day you would have to had the foundations checked over if it had been an Nokia"
But yeah, Always been happy with Motorola G phones (bar the cvamera, but I'm not really a photo person anyway), I still have an old 2014 Moto G to test apps on old devices/Android.
Last two phones have been Moto G Powers. Multiday battery life, stock Android, SIM and MicroSD cards, and a headphone jack.
Camera's definitely terrible, but I don't really use my phone camera all that much. Biggest advantage, IMO, is the <$150 price tag. It means when I trip and toss my phone into traffic, or forget to take my phone out of my pocket when going snorkeling, or drop my phone off the balcony of my apartment, I can just order a new one on Amazon, swap the SIM, and carry on with my life.
Tangential but I really miss the gestures. I'm much happier with my Pixel 6a, but I had a run of Motorola phones beforehand. God the shake for flashlight and rotate for camera were godsends. Everyone got a kick out of it too, it was always funny to see people react to how great shake for flashlight was.
I wonder if there's an app that can do this now on any phone, but I hadn't thought to look until now.
The brief period I spent with a non Moto phone got me missing the gestures so much as well. It's actually kind of insane how useful the flashlight gesture is. I realized that I actually don't really have a concept of not being to see anymore: anytime I entered a room that was too dark for whatever reason, the muscle memory kicked in immediately. Crazy.
On the non Moto phone I tried replicating it with Tasker. It worked... Sometimes. But it was a really cheap random Redmi model so that might have been the issue, more than the app itself.
It's not exactly the same, but iOS has an accessibility feature where you can map double and triple tapping the back of the phone to things like turning the flashlight on and off.
It's nearly like shaking and uses the gyros because there's no touch interface there.
Moto phones are excellent value and generally sturdy. I find myself going further and further down market buying cheaper phones like Moto G because I haven't seen a flagship feature that looks really compelling in years. Unless foldables really take off (doubt it) my main concern is really just battery and the Moto G Power is the current king.
My main problem with Moto is I've had really bad luck with their charging ports. I had a G4 and a G6, and both had ports that were loose from day 1 (so much so that car charging was impossible because it would instantly fall out) and both become unusable towards the end. I have several family members who had the same experience.
I'll agree with Motorola, though pretty-much the first thing I did when I switched mine on was disable all the Moto app stuff. Once you have done that it does mostly stay completely out of your way, which is probably the closest you're going to get to a non-bloatware system.
One slight warning, and I'm not even sure if it's completely true, but my G8+ is only a few years old and it has slowed to an absolute crawl. My current understanding is that this is because the flash storage is running out of writes and slowing down. If true, it means they used a sub-standard part with an unacceptably short lifespan.
It's Flash Player all over again! Remember when SEO became important and everyone who had a Flash website had to make "low bandwidth HTML" sites for indexing? :)
Honest question from someone who has never worked at a Bay Area startup:
What do all these developers at these tech companies do all day? As a freelance developer who has to meet ridiculous timelines all the time, I don't really get how a company can have hundreds of developers and yet the product seems to languish and/or get worse or slower or both.
I suppose there's a lot more overhead with internal QA, code review, meetings, etc, but with the amount of developers these companies have as full-time staff, what are they doing all day? Is it mostly internal systems, tooling, etc?
I just find it hard to believe that there can be hundreds of developers at a company like Twitch and yet the product is largely the same as it was 5 years ago. I would think features could be cranked out so much faster than they appear to be.
This sort of question comes up a lot when people are talking about big social media sites and there are two answers, both related to scale. First is that things really do just go more slowly when you are larger. There are more stakeholders and greater consequences to change. You don't change anything without measuring it first through flagging and limited a/b releases, and often those a/b tests actually fail to show a reason to release the change since the stats show that even though you think it's an improvement, it actually has a negative impact on key metrics.
But the second one is that while the site might seem simple and straightforward, the way it has to be engineered to handle the massive scale of a Reddit (with over a billion active monthly users) makes it very, very complicated internally. I'm not familiar with Reddit specifically but having seen the architecture at other places of similar size, I can tell you there's a ton going on behind the scenes to make it possible to reliably serve that many users and that makes major changes very complicated, involving multiple teams, and lots of planning.
These companies don’t operate like bay area startups, nearly the opposite. Where a startup is low on process and very nimble, these orgs are slow and bloated. They have too much money. They’re more like a bad corporate gig with even less focus on quality because they heard Zuck say breaking things is ok.
Peel back the layers of any site that has millions of active users and you'll find all sorts of things you never imagined would be a problem, but become so at scale because, well, people (and, well, scale).
