To add to that, a good friend of mine is a welder and machinist (and still using Linux on the desktop years after I set him up). A robot 'helper' that just moves things around and maybe does basic machine work (cutting pipe and threading the ends, for example) would put his productivity through the roof. Same story with a guy who specializes in kitchen remodeling.
It's hard to find decent general purpose help these days and they would pay good money for a halfway useful helper.
Once it's able to weld... That's going to be a massive game changer, and I can see that coming 'round the corner right quickly.
There are couple UR5 single arm cobots on eBay at $5.5k each right at this moment. The truth is that the value of humanoid is in it form, the novelty, the sense of accomplishment, not features.
If you found one for that price with the controller and pendent, please send me a link. I’ve looked a lot and have not seen any UR for remotely that cheap.
Hi, CEO of Causal here — Lucanet has been around for ~25 years and their product is very mature, but it's also very good software. Super high NPS and metrics, really quick time-to-value, extremely happy and sticky customers, etc. The UI might not follow the latest startup trends, but don't be fooled by that :)
> they probably don't appreciate comments insinuating the result is a disappointment
There is a post about the acquisition by the founders. That is the post to comment positive things about them. Whatever things any other people wants to talk about Causal product and Lucanet acquisition of it is allowed here, following the guidelines. And not poking into difficult questions isn't in that list of rules.
The .Net team has made pretty significant strides in minimizing the bundle size and I would expect that to continue. It’s now also possible to combine pre-rendering and streaming with web assembly to improve the loading experience.
We evaluated a few options and settled on Blazor after tiring of the build chain and dependency complexity of the TypeScript world. So far, it’s been nothing but a breath of fresh air to work with.
It’s important to clarify which model you’re working with when discussing Blazor. A lot of complaints seem to stem from using the Blazor server websocket model outside of its specific use cases.
The web assembly and prerendered models are more comparable to modern developments in other ecosystems.
i'm currently working on a large blazor project, and it's pretty much been the same experience as all other shitty microsoft frameworks i've used, where its super nice to work with at first when there isn't too much complexity or edge cases, and all the magic under the hood makes everything super convenient and you find yourself asking why everyone doesn't use this for everything, but by the time the application is too big to consider scrapping it or rewriting it with different technologies, the cracks start to show and it's so much work to even develop the rest of it that you start looking for another job
I live in Berlin where many people live in low-rise apartments with no elevators and keep their bikes downstairs. I believe this is quite common for many cities in Europe. What I don't understand is how people are charging their bikes. Are they really lugging this thing up multiple flights of stairs and charging it in their apartments every few days? I've heard it's pretty heavy. Or, does it not need to be charged very often?
It depends. As I could charge it both at home and at work, I would prefer to have something integrated and less prone to problems due to water/snow/ice. As I live in a cold country I really appreciate the internal hub with the protected chain which are rare to find on electric bikes under 2000 € (excluding low-quality bikes from unknown producers that have no specs nor website).
There are many companies producing electric bikes right now: I prefer to see a company that tries to do something different targeting a smaller market segments than seeing the same kind of one-size-fits-all model across multiple brands.
The "stolen" argument seems a bit odd. Sure, anything can be stolen.
When purchasing an e-bike a removable battery was a must have. The one I wound up purchasing has a pretty heavy duty locking mechanism for the battery so I never really have to worry about it being stolen.
Non-removable batteries are damaged by cold weather. Bringing it inside keeps it/you safer from theft, cold, and throwing out your back carrying your bike.
I knew that charging under water freezing temperatures could damage the battery, not storage or usage. Could you please share some details? I am evaluating to buy an electric bike, but during winter temperature can get to -20 °C/~0 °F, so it would be helpful to learn more about that.
In most ebikes (but I think pretty much all of them), the battery can be removed. Even in the ebike I own, whose battery is integrated in the frame, one can easily open the frame and take the battery out.
Ebike batteries' range is around 20 to 100 km (account something like 50% less when the battery starts to wear out). I guess that people using it frequently need to charge it at least every other day.
They weigh 19kg. Their range varies from 60km to 150km. Based on my commute, I would have to carry this bike upstairs about once or twice a week. That just seems highly impractical to me.
A friend of mine (in a small german city, not Berlin) keeps a bunch of bikes in a shared basement. I don't know the common situation in Berlin, but he could certainly charge there.
