sidhuko

It is the way of these type of early projects and generally you have some organisational and technical debt either direction but receiving downstream features while supporting legacy code is the general way in React. It was going to be a Vue 2 to Vue 3 migration but moving to React should take us out of these higher frequency changes from Vue ecosystem. I don't see you rebutting or adding anything technically here. I wasn't responsible for the original stack and no we have a roadmap for the next year or two which is the same tooling give or take. Avoiding the high breaking change libs like apollo for URQL and using their cache for simple queries and Redux when we need more.

The question is what next? Our team had already started migration from vuex to solely using Apollo. Apollo then changed their own standards like depreciating local resolvers. Vue 3 release seemed to change regularly from will it or won't it support ie11 and various other additional packages. It is fairly easy to build React-in-Vue code to do a similar migration but the "experts" in Vue often just live in the short term without really committing too a level of support that an enterprise team needs with 20-30 developers. With React I'm sure any major changes will be a phased thing so I can continue to upgrade through the major releases for new features while updating code to new patterns. There is usually codemods to automate any changes because the coding patterns are highly developed to be testable and consistent to change. Similar support exists around the community of packages like Redux. Vue is stretched across multiple projects like state management, build tooling and DX while genuinely being behind the curve in best practices like testing and static code analysis. A Vue 2 to 3 migration is really a complete overhaul of every component to allow you to upgrade to v3. That is a huge liability of an inexperienced team who I expect to make similar mistakes with their community.

Yeh it is why I put Vue as a great web application framework for developers not specialised in frontend solutions. They've been fragmenting their community there by becoming an SPA framework to compete with React. Vite is a good tool but we have many others that are simple to use. This one is just has 1st class support for Vue because it comes from the core contributors. The general ecosystem for vue though is a third party package which integrates something like vue and apollo together. Which is not supported by the vendor and falls behind major releases or makes drastic changes to fit new major releases of the Vue framework. You will find a lot of vendors not supporting Vue directly and those unmaintained projects are leaving you behind in feature set or using new anti-patterns and creating tech debt.

That isn't a thing from Vue3 though. It has come from esbuild and swc projects. Both are now looking to fully support typechecking in a lower level language rather than having JS tooling written solely in JS. You can use vite for React too but it does lack certain features for us. I could get reasonably the same gains using webpack with swc loader or esbuild loader too. It is really just a preference on type of projects. For small starter applications a tool like vite is cool. If you're looking for ways to distribute many common applications with shared vendor libraries and seamless transition between microfrontends then federated modules is a big feature of webpack.

I joined a company with a Vue app just before the Vue 3 release. I don’t think anyone believes it was a soft launch. Then the tooling like nuxt did the same with a v3 release countdown timer which only then released it was in beta with no support in their ecosystem. You could pay 10k for a consultancy though. I only wanted webpack v5 to be able to use federated modules to give us more migration options. The whole experience reminds me of Angular.js to Angular so I was quick to jump ship and spend the migration effort for v3 in moving to react. We spoke to a contributor too that basically told us we should wait for v3 because currently it’s not really built for SPA. Vue 2 was a web application framework and I could see the benefits for php/python/ruby frameworks with losing JSX and being more understandable for fullstack engineers in smaller teams who might not know React. They have now made a direct competition with React though and badly implemented a lot of apis (simple things like grepability and codemods are lacking). They struggled with this release for a year and now they are still behind where React is focusing on server components, concurrent rendering and the tools we need for WASM to be implemented in the most performant ways now ie11 is officially leaving support this year. Some have said it here too that the whole ecosystem felt beta and now the largely community based ecosystem is either leading to vue3-* packages which just make an upgrade to Vue 3 a full on migration.

I’m 32 and in a similar situation. I lost my mother and both brothers within last 6 months of last year and ended up questioning everything.

Even though I was in this moment of time where I was questioning everything I couldn’t actually move forward with any of the changes I wanted. The big mental changer for me was the gym. Not necessarily for health but because everyday I’m pushing myself to failure and also seeing improvement.

Even though I have hobbies like photography and being a drummer to be honest I would be frustrated at that type of failure and avoid it. Maybe the lack of feeling creative is too personal to face right now. Since the gym I feel like that’s improving and I am slowly reaching out to a social circle again and seeing new opportunity.

It has improved my mental clarity and personality too. I am lucky to have my girlfriend of nearly two years and I was preparing to propose before all this happened. I would question that too but I started to realise I didn’t want to be this person running from my problems in different countries again. I didn’t wait for the perfect time but did the best I could and that went well.

I suppose for me in the area of finding a partner was finding faith in myself again. At around 30 I was about the same and hadn’t been with anyone I could see marrying. I couldn’t seem to attract the type I saw myself settling with. I think that changed with the gym too and applying focus to my new interests at the time like photography.

After I stopped trying with my current fiancé, maybe a year and a half of our first meetup, she started to see who I am and what I could be because I was just applying myself to improve my own life. I think we all like to see that in each other no matter gender or preference. It can just be within your friendship circles after you grow out of drinking buddies.

I think you know it’s not your too old to go out a be that guy again but you don’t want too. Trust me I have old friends your age who are still acting like their 20 and reliving all the same mistakes. Right now you just need a physical parallel to what your mind needs to do. Fail early, learn and adapt, improve and grow

Looks like an enterprise version of discord.

Integrated sensors really. Things like AF would work on different sensors in DSLR. Sony removed the mirror and put everything on the sensor. Fast AF tracking, shorter distance between sensor and lens so better low light capability.

This is the answer really. Wealth accumulation and powerful enterprises lobbying and dividing societies in their own interests. Whether its BP making you believe your own carbon footprint offsets there or social media giants playing to one-side in an election to keep favourable rules in place. You won't see this common sense in politics though as it would open more competition if they weren't able to using lobbying to support their own reelections.

Better learn chinese then.

> We think that Auth0, Firebase etc are great services but auth is complex.

Yep that tends to happen when you are supporting SSO and certifications like OpenID Connect. Using one SSO portal to handle mobile, spa, web apps and code auth with evolving techniques like PCRE. That's probably why some customisations are not available too because it breaks the standard. You will just end up with the same models once you've implemented all the same features. Okta, Auth0 and others are all really similar because of the standards behind them not because they thrive to be complex.

I built an app for major sports company in the UK several years ago now. The choice as actually the most cost effective. Most providers of the data, usually collated by people using an Xbox controller and relay device in the stadiums, are uploading static files to storage. We used a thin node.js layer to stitch these from a connected volume and expose them via an endpoint which would specify a time range. If a user never requested the results for the 36 min in a game then our solution wouldn't have to do any work. Once we did process a request for a user for a game at a given time range then all other users would then receive the same cached result. It was very cost effective when you compare millions of users requiring websockets and processing all the events regardless of whether someone is watching those results.

And being far from trees and buildings.

Germany had 1 million microgenerators in 2008. Just because you don't see them...

I posted another comment but john Deere did this and had to remove sites in the US because of ecological harm onto farmers. We have a lot of them around my area too, my uncle installed most of them, the 1-2MW are really a dent when you see the size of US wind turbines

It's a bit like the agricultural business. Large scale investments only leading to poorer soil quality. The economies which have adapted best have taught their own citizens to farm energy and benefit from using it with climate taxes.

Have a look into microgeneration and verticle wind turbines. That's where wind is strongest.

Not efficient enough to compete at scale with wind or solar.

You can't live close to a wind turbine as large as they are being built today. At least not with sound and shadow distance. Have a look into stories going back 10-15 years into living with the flicker and sounds.

It's not surprising research is catching up with environmental groups from 10-15 years ago. I started a wind turbine business during FiT rush in UK ten years ago. At that time, John Deere in the US was removing a large wind turbine farm because it impacted on ecology hundreds of miles downwind. We already had studies to show it drastically affected bat and bird colonies who would have fatal lung collapses (explosions) from the air pressure differences created by the huge blades. There was a growing understanding from those in microgeneration (under 50KW) that mass scale adoption would only be possible with small units which are less efficient but also easier to access and fix. This is the successful model in germany. If 8% of UK land is urbanised then we have huge expanse of existing high rises to tap before we should planting these sites on areas of significance (coastal, large open areas)

"Job quitting and breaking up both carry very large, positive, and statistically significant coefficients at six months. Going on a diet is positive and statistically significant at two months, but has a small and insignificant impact by six months. "

Guy breaks up with girl Goes gym (2 months) Guy finds girl (6 months)

I'm sure we have these chemicals which effect emotion to be overtly opportunistic about life around periods with new sexual partners to encourage reproduction. But I'm just an alien

Social programs should really plan for these types of disruptors more often. We've had Asda (Walmart to you US folk) trying to do the same by adding boxes of below commercial grade into supermarkets couple years ago. It really pressured our local small suppliers by people seeing the cost of two trips higher than the difference in prices. I don't think the author should feel more cornered though - imperfect food still makes perfect meals at a higher margin - perhaps they should use this encouraging response from their community to take their stock, teach to cook healthy and retain profitablity to support their existing programs? They would even be able to maintain a reliable % for food banks and reducing waste by converting excess into food for a later time.

We are such a totalitarian part of the species. Someone writes about microservices and my next project I'm building services for each feature because some manager heard it increases reliability. The fact is its always science. If you don't want your inconsistent dataset from somewhere else in the corporation taking down your application then chunk a part of the application into your own container to manage calls rather than allowing the event loop to block up. It doesn't have to be 'micro', it has to exist for some reason, if not it is just your developers trying to be cool.

I wonder why Ripple isn't getting more coverage... I told my father to cash out last week. Ashamed he didn't as he would of made his win and could reinvest at $1.10 again.

Have they sorted the differences with async/await? I'd be using if it wasn't from the different implementation meaning you need to use typescript to babel.

So you need to get an access token by validating against a third-party (keycloak, auth0) to access your own API? That's a pain.

For applications using a HMAC token with some sort of timestamp which can be checked for replay attacks. AWS has a good guide: https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthenti....

For users, I'd add a OAuth layer to the application layer and still have this application using a HMAC like above. You want to try keep things 'stateless' when it comes to your API's.

For users or applications within your own network?

48 now. Ripple's being hit hard.

What I've found having to use serverless is the local development tools are broken. You'll find cloudformation is the only way to reliable manage all the proprietary paid for services which will require you to read several documentation on various tools (kinesis, dynamodb stream or fifo, standard queues) to work out which one might work. To find out it doesn't necessarily work in your applied function (CloudWatch Insufficient Alarms I'm looking at you). So you then have a choice to use cloudformation and another deployment tool to push your services. This is more typical after you've given up trying to manage dynamodb-local across platforms for your codebase.