Others who are happy with the gains they have made, and think it's too risky to keep holding. I've got a friend who sold his bitcoin recently to buy a house.
Unlike companies which have revenue as a marker, the bitcoin price seems very speculative, and if you think others might sell at 40k, you might do the same.
> Others who are happy with the gains they have made, and think it's too risky to keep holding. I've got a friend who sold his bitcoin recently to buy a house.
Yeah I'm not surprised about moves like this. 35k+ is when things start to get interesting.
A few years ago I grabbed one at $1,200 and then sold it like 6 months later for around $1,800 because I was like "cool a 50% gain".
If I had held onto it, selling at 35-40k seems reasonable because even after 15% capital gains tax that's enough to live comfortably in the US for an entire year. That's a life changing amount of money.
That's the other factor. At what point do you decide it's gained enough and make sure to cash in?
How many people have the discipline to buy something at $1,000 then watch it increase to $5,000 and not sell if it starts to come back down? Now imagine when it went to $20,000 previously and then back down to $6,000.
There's nothing wrong with cashing out. Can't go broke taking a profit.
We’re sending this note to let you know that, on June 30, 2021, the Poly website will be shutting down. The ability to upload 3D models on poly.google.com will be shut down on April 30, 2021.
What does this mean for you?
Your assets will be available at poly.google.com until June 30, 2021. You can download your entire library at takeout.google.com/settings/takeout/custom/poly, or you can download individual assets by viewing each asset’s page. After June 30, poly.google.com and associated APIs will no longer be accessible. You will not be able to upload new 3D models on poly.google.com after April 30, 2021.
We want to thank you for joining us on this journey. We appreciate you trusting us to host your assets and provide a space where they can shine. The amazing work that our users have uploaded to Poly every day has surprised, humbled, and delighted us, and we have you to thank.
For more information, view this Help Center article.
"If you choose to open a full current account with Revolut Bank in the future, any funds you deposit will be protected up to €100,000 under the European Deposit Insurance Scheme (EDIS)."
"Microsoft has illegally tied its Teams product into its market-dominant Office productivity suite, force installing it for millions, blocking its removal, and hiding the true cost to enterprise customers"
Is teams auto installed with the Office suite and can it not be uninstalled?
Yes it is auto-installed and auto starts and is very annoying to get rid of, as a sysadmin. It also installs itself per-user, so non-admins get prompted constantly to install it themselves and can do so even with limited privileges. It is persistent.
What's the annoyance? It's an MSI. Use msiexec /x to remove it (probably via PDQ Deploy or SCCM or a PowerShell Script), and then block the installer from running again during an Office install with GPO [0]. It's definitely easier than cleaning up some of the other garbageware in Pro.
I’m not sure on Teams specifically but years ago (last time I tried to install the Office suite) you had to install basically all or nothing. I just wanted OneNote but the installer forced me to add Word and Excel and Powerpoint, similar to this forum post: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_...
If they’ve added Teams to that installer, I’m not surprised.
>BUT, if you are willing to invest a little effort, there is a business specific tool you can use. It is called the "Office Deployment Tool". You will have to edit a simple text only "XML" file that tells the tool what you want it to do.
Under normal circumstances Teams can trivially be uninstalled - it's just an Electron app. I have Office and Teams installed on my PC and can freely uninstall or install either of them, and I had to install Teams manually. The android and iOS Teams apps are definitely manually uninstallable.
My guess is they may be referring to enterprise setups or perhaps an enterprise office 365 installer. I'm using 365 but not an enterprise 365 account so I can't speak for how it would behave there. Bundling Teams in with the other stuff that gets installed might be an option individual companies can opt into.
Certainly wasn't in our case (EU E3 or E5 licenses). You can also disable the license for all users. Now, the practice of enabling licenses for new apps by default could be improved...
True, that may be the case. There is config.office.com where you can adjust a lot of behavior (you need an admin account I believe). If teams gets installed with office on default settings, you can certainly change it there. However, I don't think we have changed anything there and it didn't get installed automatically.
I think the application proper can be disabled, but it's built into basically every Office application at this point, as far as I know. It's like wondering if you can uninstall ffmpeg from an Electron app.
Which results in much less js code shipped and better perf. Browsers have caught up to (almost) everything jquery does. Thanks jquery, you served us very well!
I agree the API and the chaining are nice in some cases. And I agree that native JS is less pretty.
But I personally don't use it anymore since a while now. I either use React/Next + Redux if they are a good fit, or just plain native JS otherwise. JQuery doesn't solve enough of a problem (anymore) for me to be worth loading and adhere to.
If I do the latter then my code is often structured the same (per module).
- defining some utility functions
- setting up state and state-transformation / "top-level" functions
- getting the DOM elements (once)
- defining DOM mutations on those elements based on the state, usually call these "render" functions.
- registering event handlers on those elements which call the top-level functions and pass the new state to the render functions.
I know this is kind of a dumb/rigid approach, but it suits me well. There is not much obvious use for jQuery here. The only place where the nice chaining API would be useful are the DOM mutations (sometimes) but I haven't found this to be a huge deal.
As soon as I need to do more AJAX, inserting/removing whole Nodes/NodeLists, have more involved state management and policy then jQuery doesn't help anyways and a more sophisticated framework is more fitting (like React/Next + Redux).
It's debateable whether jQuery is a library or a framework. It's definitely at the frameworkey end of libraries of the libraryish end of frameworks.
But if you'll admit the terms get murky in the middle then I think it's not controversial to assert that a framework can depend on a library without it offending the gods.
So we're very quickly in the territory of "things reasonable people could disagree about" and quite far away from "glibly asserting that something isn't even up for debate".
Unlike companies which have revenue as a marker, the bitcoin price seems very speculative, and if you think others might sell at 40k, you might do the same.