Aren't these components that should be ok at least after 17 years of Tesla?
After watching Rich Rebuilds on YouTube I came to the conclusion they are just not very good cars.
1,907 karma · joined November 5, 2019
Aren't these components that should be ok at least after 17 years of Tesla?
After watching Rich Rebuilds on YouTube I came to the conclusion they are just not very good cars.
Not in this case. Only when they could have prevented that employees were reselling the devices.
It looks like GEEP agrees with Apple and they are going after the people who resold the devices.
But keep in mind that the audio of most monitors is just bad.
Money as metric for success leads to destruction.
Someone who helps a stranger is successful.
I wish more people would understand that everything that devides us as humans leads to destruction. Everything that unites us leads to good things, which I call success.
* FreeCAD - Very powerful, very buggy/unstable.
* SolveSpace - Very powerful, takes time to understand the interface.
* OpenSCAD - Great for simpler objects.
* Blender - Not very good for CAD modeling, but with non-destructive modifiers and the new Extrude Manifold it can be used.
Personally I use Blender all the time for 3D printing. There are some tricks that can help a lot with precise modeling. For example you can draw a plane, but instead of extruding it you can use the solidify modifier to give it thickness. Then the thickness is non destructive. You can also view all edge lengths which help you to check if everything is ok. Since v2.9 you can now use Extrude Manifold which is not precise but works a little like Sketchup making some modeling much easier.
And a lot of time my workflow is: Create something in FreeCAD/OpenSCAD -> export to Blender (STL) -> add finishing touches -> 3D print.
The people are not talking about free software as their right. It just sucks the price went from free to ~$300/y.
We all know Autodesk can do whatever they want. But they created an expectation by providing free features for years.
All they did is make people loose trust in them.
Most personal users will just move to other free or cheaper software.
Exactly for the reason shown in the article.
I believe right now it is still too difficult to do this in any framework. That's why developers take shortcuts and just expose all entity data or just make a mistake and forget about it.
Does anyone know if such a framework already exists? So per field rights, not per entity rights.
Maybe you also like this talk of Andrew Sorensen on live coding music for inspiration: https://www.youtube.com/watch?v=yY1FSsUV-8c
Or automated invoices. It is much easier to change this than changing a co-worker who manually created all the invoices.
I don't think they were linked from the document on github.
This is not the point. The point is some developers just include big Javascript files because they don't know what other methods and options there are.
I have seen developers include Javascript to 'fix' things across browsers but it made things worse because the `let` keyword was not supported in some browsers at that time.
So it is not about if you should use Javascript. It is about the fact a website or webapp can and should be fast. But when a developer does not know about the technical aspects we will end up with multi-megabyte pages that take 10 seconds to complete.
--
About the `position: sticky`: it is not smart to promise a client a pixel perfect experience across all browsers (unless they want or need to and will pay the extra price). In the case of a sticky header you can support all modern browsers with two lines of CSS (`position` and `top`). The other 6% won't have a sticky header but still a perfectly working website. So imho you did not caught a mistake but a real world example.
I have seen websites where the homepage's HTML alone was over 1MB! in size. The only thing that got exited was my CPU.
Let me tell you: if you want a header with a background image where the text is aligned at the bottom you can just write:
<h1>My header</h1>
There is no need to write it as: <div id="mainHeader"><div class="align-text-bottom"><h1>My header</h1></div></div>
And if you want to stick the header to the top you can use `position: sticky` in CSS instead of including a huge Javascript file that can do all kinds of fancy stuff you don't need.But I am not sure I can blame those front-end developers. Deadlines are tight and it takes effort to learn about the technical aspects of front-end development.
My personal standard is that a page should be ready in 1 second. For huge sites 3 seconds max. I've been creating small and huge websites for over 20 years now and never had a problem with these goals. This includes webapps built with Javascript.
Currently I am working with Blazor (C#) and I really like that you can forget about Javascript (most of the time). I believe Blazor, LiveView and others are the future for webdev.
Can you explain something more about why you think this is not a good thing?
Is it like Laravel (PHP)? Lots of magic so it is very easy to get started but a hell to maintain?
I really like to get started with Elixir (for webdev) but I am not sure if I should start with Phoenix.
The main reasons are that they can transfer heat very easily and they do not contain much water relative to their volume.
So there is probably a lot more life that can withstand extreme conditions.
The hockey puck is just worse because it's hard to see which direction is up.