Haven't really used much other stabilization in post after modern gopros have gotten so good. Especially with the 360 variants (MAX and now MAX 2), it's buttery smooth (and infinite FOV means no cropping). Sometimes too smooth, I want to show how rough the cycling trail really was!
With very good daylight, Hypersmooth of Gopro is ok, but as soon as the conditions are a little bit less than ideal, watching the videos that we get out of the Gopro makes nauseous very fast.
Is this specific to US culture? And what about your work environment makes it such a risk?
Where people are laid off here (Norway), they're still employed by law for 3 months. Most companies don't force you to work all that time, but it's pretty common to finish up your tasks, do offboarding etc for a few weeks. Never considered it an issue. Maybe it's a high trust society thing?
>Is this specific to US culture? And what about your work environment makes it such a risk?
It's called garden leave, it's popular everywhere, especially if it's a big international company with diverse workforce, sensitive to IP rights, since there's been plenty of cases of people taking company IP on USB drives to the new employer, like that Indian guy who took IP from Valeo to Nvidia and got his home raided by the police because the Valeo guys saw him share it on a Teams call lol. Same for companies in finance or that handle sensitive information. Norwegian trust doesn't fly anymore when it comes to multinational corpos.
Companies run on liability and risk mitigation. If something bad happened once (IP theft or sabotage from someone they let go), then they have to prevent from ever happening again, not keep blindly trusting people while letting it happen.
It is not that common in Norway. It has at least been argued in the past that working your notice period is not just an obligation to employer if they want to enforce it, but a right for the employee on the basis that being walked out can affect your reputation by implying possible misconduct exactly because it has generally been uncommon in Norway.
I haven't worked in Norway for a long time, so haven't kept up to date on the current legal position. The typical argument used to be that if there were concerns over IP theft or sabotage, there were other ways of protecting against that - and indeed, insider risk is something companies need to deal with whether or not someone has been fired.
Garden leave isn't for when you don't want to force people to work out their leave, but when you want to force them not to, and as the very next clause of my comment pointed out ("but a right for the employee"), it's not a given you can just do that in Norway. Most of the time, employees will be happy to be told they don't need to show up. Sometimes they aren't. There have been lawsuits over attempts to force people on garden leave in Norway.
What's stopping people's from doing that while employed? I think if you treat your employees with respect, they don't feel the need to this kind of retaliation.
So stealing IP, breaking the law and your contractual obligations, should be allowed if you feel like your employer isn't valuing you enough?
That guy was a six figure paid SW engineer, who stole IP for the opportunity to jump ship to an even better paid gig at Nvidia, not a minimum wage fast food worker who couldn't take it anymore.
Scammers will always be scammers and will use any excuse and opportunity to get ahead, no matter how much you trust, value and pay them, they'll always want more from you even when you have no more to give. They'll bankrupt you gladly if they can get away with it, out of greed, envy, spite and malice, I saw this when my parents ran a small business.
In globalized multinational companies, you can't defend from this using mutual trust and respect, only by strict IP protection, law enforcement, fines and jail time as a deterrent.
> So stealing IP, breaking the law and your contractual obligations, should be allowed if you feel like your employer isn't valuing you enough?
Please don't straw man me. Discuss in good faith, and don't invent things I didn't say. I never said anything remotely close to that being allowed. I said that it could happen even if you don't terminate all their accesses the moment they're let go. And the fact that some people have to worry about it reflects on how the employer behaves or the trust in the society.
>Please don't straw man me. Discuss in good faith, and don't invent things I didn't say.
I'm not. That's just the only logical takeaway from your comment saying: "I think if you treat your employees with respect, they don't feel the need to this kind of retaliation."
How else would you interpret it, rather than a veiled threat that if employees don't get their way then they'll steal or sabotage you? Please explain in detail. If you feel you're not treated the way you want to, then quit and find another job, don't steal or sabotage your employer.
> I said that it could happen even if you don't terminate all their accesses the moment they're let go.
Yeah, but it's WAAY more likely to happen AFTER you give them notice of termination since breaking relationships be them romantic or employment, can cause people to do illegal things like steal from their employer or murder their spouse in an impulse of revenge, when they hear their relationship is being terminated. All this is documented from decades of police and legal records, and companies know this, so they take preventive measures.
>And the fact that some people have to worry about it reflects on how the employer behaves or the trust in the society.
Companies worry about it because some people are gonna be evil thieves no matter how well they're treated.
If you want to get better treatment then negotiate better, talk to lawyers, organize in unions, vote, go protest, pester your representatives, but don't break the law or steal from your employer in revenge, as that reflects badly on all workers, and the economic, legal and societal costs of a few thieves will be distributed on the honest ones in forms of more workplace surveillance, higher cost of doing business, higher insurance premiums, etc all of which have a negative upstream effect on wages and employment opportunities.
You're kinda proving my point, though. It seems you live in a low-trust society where it's eat or be eaten, and where employers and employees regard each other with disdain. So your only way of interpreting my statement is that it's a "threat". But it's not, it's about mutual respect and good relationships.
Which is what makes it hard for you to fathom it doesn't have to be that way you experience. When my company laid of half it workforce two years ago, everyone stayed for a few weeks to help in the transition, with the same accesses as before. Because we were treated nice all the years working there, and with respect during the process, it was absolutely no ill feelings or any risks of people doing what you describe.
So again, please read and answer comments in good faith. It's your mind that's not open enough for alternatives here, please bear that in mind - don't use your own closed mindedness to misread my comments.
Edit: your other comments in this thread shows you absolutely loathe your employers. I feel sorry for you having had those experiences, but don't assume they're global.
I have had this (garden leave) specified in contracts in Norway too - it's not strictly a requirement that you're allowed to serve out the full 3 months, but the default unless specified is 3 months. In the cases I had it in the contract, the contract generally framed it as if some other perk (like shares) served as consideration for giving my employer the right to put me on garden leave.
I agree. My kotlin is readable. The functional code with typing all the way tells what every step is doing. My same code in python is a hot mess of nested list comprehensions and lacking lambdas.
The lock would normally make the second request wait, aka not return a response, until the first one is done. Then it sees it's a duplicate and returns that. Or it times out and returns an error. Then the client hopefully have some exponential back off strategy, so the third attempt doesn't suffer the same fate.
Most courses I've taken have obligatory assignments that are pass/fail, and you have to pass a certain amount during the semester to take the final exam. But the grade is determined entirely of the final exam.
Which to me seems the best way, you still have to learn throughout the year. Especially to avoid cheating this works nice. And as an aside, most people I know that did a year abroad in the US got 1-2 grades higher, as it was quite easy to just farm extra credits.
> The alternative would be that each school develop their own platform for this
I worked at a university which did exactly this, in the UK.
It was a bespoke platform which integrated incredibly well with the rest of the systems the university used because it was designed from the ground-up to meet the institution's needs, there were regular user groups involving academics to understand what features needed to be built/worked on etc. At one point it was all OSS on GitHub too, in case other universities could've found it useful. It handled plagiarism detection (integrating with Turnitin), marking, exam grids, coursework submissions and feedback, seminar allocations, personalised timetables & mitigating circumstances.
The in-house dev team was vastly cheaper than anything SaaS would've cost, as well. It also maintained software for on-campus parcel deliveries, online exams, opinion surveys, a mobile app for students/staff, the SSO system, the course catalogue, car parking permits, a content management system and more.
My (also UK-based) university has been working on a new student records management project for years that's been incredibly ill-fated. It's destined to replace all their current systems and the first module module was meant to launch last year, except it thoroughly failed testing and nobody has heard anything about it since.
No idea how long it'll take to pull through. I don't believe it's an in-house effort.
In-house bespoke software sounds reasonable, and multi-customer SaaS sounds reasonable, but outsourced bespoke software sounds like a complete dumpster fire:
End users who report problems:
* are ok with IT level 1 telling them IT level 3 is working on it with velocity appropriate to keep their jobs,
* are ok with IT level 1 telling them ${vendor_of_well-known_solution} is working on it with velocity appropriate for many customers, but
* are not ok with IT level 1 telling them ${vendor_of_bespoke_solutions} is working on it with velocity appropriate for one customer (if they even still exist).
Or it's just another example of why FOSS fails - people (like you) expect free labor and never want to pay for it. They tried to make it a sustainable project, and it would probably have died even earlier if they didn't.
> For the last 5 years, PySimpleGUI offered free software with the hope of sustaining the project with donations. We appreciate the support we received, but the amount has been too small to support the project.
I don't think this is a complete characterization of what happened. From looking at a previous thread (https://news.ycombinator.com/item?id=39369353), the owner curiously did not allow outside contributions to his GPL project. This is odd, especially if it seems like he was complaining about having issues with maintenance of the project. Then, after he tried to switch the license, he deleted/obfuscated the repo history. Even though it is GPL, because he had the "foresight" of not allowing outside contributions, he was able to take this action unilaterally. I suspect that the owner had his mind on commercialization from the very beginning, and was using the whole FOSS bit as a way to get free publicity before rugpulling.
> with the hope of sustaining the project with donations.. the amount has been too small to support the project
So shut it down, lock the repo, invite new maintainers indefinitely. It's only non-sustainable for the price the author is asking. It'll still be FOSS even if no longer maintainer by the original author, whether a new maintainer steps in or not.
And if they want to fork it an create a commercial alt, no problem - anyone can!
The problem arises, IMHO, when they develop (accept contributions) or propagate (lock-in) a FOSS project in good-will, then somehow leverage their position as a FOSS maintainer transform it to non-FOSS.
I think that was a very constructive comment about the unconstructive way people are shoe-horning other concerns about bun into this thread abut a specific aspect which itself turns out to be just an experiment that someone knee-jerk reacted to, despite several active threads already discussing those matters one of which only just fell off the front page.
While the concerns many have about Bun's potential future direction are valid IMO, of the posts on this thread the one you are criticising is one of the more constructive.
reply