MentallyRetired

`The dual approach of marrying a Single Page App with an API service has left many dev teams mired in endless JSON wrangling and state discrepancy bugs across two layers. `

Umm... not it hasn't? Separating the backend from the frontend allows for multiple frontends on multiple types of delivery. Outside of edge workers, how is HTML-over-websockets supposed to compete with a good ol CDN (jamstack) on TTR?

What is that, per-capita vs other states though? Curious how effective californias measures are, currently.

As someone who's been making websites since 1993, everything you said here has made me twitch in one way or another. I've been a ColdFusion team lead, a PHP developer and I used to write DHTML scripts.

Also RIP to separation of concerns on the frontend (document [html], style [css] and behavior [js]) since it's all buried in javascript nowadays.

Let's talk about Zuckerberg wanting to rewrite Section 230.

I also agree. "Federated" is not a killer feature. Simplicity is, and that needs to be a priority.

This has been around for years. It's a solid service. With Mixer's FTL it added normal amounts of delay, so that kind of sucked, but no need to worry about that now, I guess.

I've heard of this happening again and again lately because of the lack of traffic due to Covid.

How do we accelerate this process?

We're not a communist dictatorship.

Came here to share Ackee. I haven't used it yet but it looks really nice.

Right? I'm at 22 years professionally and I feel like a dinosaur out here.

As a developer, how do I lend my support to stopping google from trying to steal the web?

Something actionable, something specific to my semi-unique position as a developer?

Hi Tobi,

It was the change on limitations for variants. We woke up one day to product additions failing. Took about a week for the tech team to figure out that we were being throttled because we were exceeding 50k variants. Totally understandable in the bigger picture of things, but I didn't feel we received adequate warning. Developer support had told us that sometimes they grant temporary exemptions but in our case they refused. They advised we upgrade to shopify plus (they quoted us over $2000) to remove the throttling/limitation. Financially it was out of scope for us, so we had to throttle our own customers, which led to a massive disadvantage.

I ended up writing our own cart software, which was always part of the plan, but in the meantime our business suffered.

I don't hold any grudge about it since we were getting incredible value out of the previous arrangement, and I do think Shopify is amazing software. I've been a paying customer in multiple capacities since at least 2008 and recommend it to people all the time. What happened was just unfortunate timing for us.

Thanks for taking a minute to listen, though. Much appreciated.

It was a limitation on the number of variants. They had no limits prior to this API update I'm talking about. My business allowed people to create merch and we'd add it to a collection on our storefront. Developer support told us sometimes they grant temporary exemptions. They did not. They told us we could upgrade to shopify plus which has no such limitations, but being a bootstrapped company we couldn't swing the $2k per month.

Edit: Just to be clear, it was always on our roadmap to migrate away from Shopify's platform, but they accelerated our timeline and we had to limit the amount of merch our customers could add which obviously led to upset customers.

We're still operating, albeit close to insolvent, and have since launched our new platform. But our reputation has been irreversibly damaged.

Shopify made a change to their API that was easily measurable on who it would affect, but didn't email us. Refused to grant us a temporary exemption (they would do it for $2000/m they said). The end result? They've sunk my business. I've replaced shopify now by writing my own but it's too late. My customers have all gone to my competitors and we're looking at pivoting.

Right? It's almost as if they have expenses to pay for. They provide value and they're entitled to earn a profit off of it. As a small business owner myself, I'm surprised by the amount of people who expect everything to be free.

I love this idea. I don't understand why, in this day and age, I need a kitchen in my house. I'm not a chef. I don't have a wood shop or an auto shop in my house. I don't grow my own food or have my own cows. Cooking for myself seems like an old fashioned kind of thing to me.

As a Firefox user, is there a reason to convert? Seems like a step backwards to me, even though I applaud what they're doing.

OP on the thread and actually I'm a former disney dev for disneyworld.com. It's a sweat shop. They had me working 100 hours a week the first 4 months I was there. They would order me food so I wouldnt have to leave my desk. Many times I slept under it.

Then I had 6 months of pretty normal hours working on maintenance, then I went back on another project and they had me working 60 - 80 hours (with some 40 and some 100 sprinkled in) for 18 months straight before we finished the project and I bailed.

Great resume builder but be prepared to put in hours.

I don't think anyone on hackernews would be surprised by this. The scale they have to operate at is absolutely insane. To scale flawlessly on day 1 is a big ask of any development team.

They help pay the bills, so I don't mind addons like pocket even if I don't use it.

I worked at a company called Hydrogen Media in St Pete, Florida. We had a bell that would ring only when we got a million dollar deal. It rang multiple times a day.

Our office was insane. Exposed rafters with the trusses and everything painted black. Our walls were deep blue but had blue neon running the length of the room on all sides. No overhead lighting.

Our developer floor was elevated with sub-floor network cabling. We had a dev floor about 100 yards by 50 yards, the size of a football field, roughly. A little shy of that. Private offices had glass walls facing the dev floor. Our sound studio (these were the flash days) was a hollowed-out VW bus in a soundproofed room.

We had a fire pole from the bosses office down to the dev room, conference tables with in-layed TVs. It was pretty wild.

In my time there, I built ~400 replicated sites for Colliers realty, DuPont Registry's website, a bunch of websites for the Tampa Bay Buccaneers, the Tampa Bay Lightning's website among others. We were printing money.

The crash hit hard, and Hydrogen Media dwindled. Massive layoffs, and eventually it renamed to Bayshore Solutions and relocated to Tampa where they still do business to this day.

I think this is perfectly acceptable, especially since they've announced it ahead of time.

Between this and Iraq, it's a tough week for access to the web.

What exactly was cloned? The look of it? They still had to mill the thing from aluminum, design the components to fit and operate well, and everything else that comes with developing a laptop. It's not like they even took Apple's frame and copied that verbatim.

In fact, they went a step further by including some features that a Macbook doesn't have. Apple doesn't have exclusive rights on aluminum frames or the color silver. Or black keys... so what exactly did they clone, really?

Nice article. Sad to see Timelinr not mentioned, though.

Hasn't PayPal been doing this for decades?

I'd ask what third world country you live in, but it really sounds like America right now.

I once implemented infinite scroll that 1) didn't auto-scroll from the first page, you had to click to continue and then it would infinite scroll. This way, people could see the footer and didn't have auto-loading content unnecessarily and 2) the infinite scroll worked bi-directionally. 5 "pages" would be loaded at any given point, with the goal that the user would be on page 3, in the middle of the stack of pages. This way, memory was kept low, and we even implemented the History API so you could link to the pages by post ID.

How will this affect platforms such as amazon or redbubble?