Thanks for taking the time to find/share these links! Very informative.
It sounds to me like most of the criticism's outlined are solvable. Perhaps the people behind the standard should be engaging the framework community more.
I wonder if you think web components (and the problem they set out to solve) is wrong from a fundamental/architectural standpoint?
Web components seem like a good idea to me. I would imagine there are a lot of libraries out there (eg/ calendars, styling frameworks) that would benefit from reuse across applications. The browser could cache it even if served from a different CDN.
I'm curious what the problems are with web components that you see? Is it specifically related to how they might be used (or useless) in the major frameworks?
Frameworks like react/angular/backbone/vue solve the problem of creating a single page application with a nice architecture and sharing code between components within the SPA.
Web components solve the problem of sharing code between any application.
There are opportunities to share code (eg/ data binding) and I believe that is the case (they use the same underlying browser APIs where available)
A few years back I did something called 'master the mainframe' where they provided a TSO login for you on an instance running in one of their labs. They also provided you with a bunch of fun exercises to learn more about the system.
I love the idea of requiring the purchase of merchandise beforehand, although I'm not sure if this would only compound the problem of scalping. The problem with building moats is
a ) scalpers will write algorithms to predict where the moats are before fans can get there
I believe the problem they cited with this approach is it provides a poor UX where someone would have to keep checking the site to see if the ticket price has hit their desired target.
It would also still leave room for bots front running although still a better solution since the effects are dampened. Still, it's a lot easier for a bot to watch for a 'good price' to come up than a 'true fan'.
Perhaps to get around that there could also be an ability to make automatic purchases for a user once the ticket price reaches desired target? Something like a batch auction that randomizes winners in a cohort might work.
There are also people working in this area that would like to simply prevent resales. The problem there is it also might discourage purchases since people might be more reluctant to make such a big purchase if there is no way to recoup their money in case something happens that prevents them from going.
Perhaps another alternative to discourage scalping is if there was an identity system that requires each ticket holder to prove their identity. That, however, would also decrease the UX dramatically and would be a tough sell. But maybe the time is right to make such a hard sell?
I think the core ethos of the book is every negotiation is different and so each tip/technique is just that - a tip/technique you can add to your tool belt and use when the context lends itself to it.
The book also mentions anchoring should usually be avoided in negotiations and instead it recommends you focus on the non monetary value points each party can exchange.
There is actually a section on negotiating salary and IIRC it recommends you provide a range where the bottom of the range is where you are hoping to land.
So you are correct - I would never say in a salary negotiation that I need an exact dollar amount as it might make me love petty unless I prefaced it with 'I have a family to feed and a roof to put over our heads'.
I have also been loving yoga on youtube! Its like going to a class except there is nobody to tell me how much my form sucks.
I've been thinking about writing an app to let me turn some of these follow alongs into an interval timer where I could just say the name of the pose (so I could do other things while doing the yoga). Then I could always click on the pose to go back to the video. Does that sound of interest?
I've been using it more to read Dalio's articles. Which makes me curious why he is using linked in and not just hire someone to set up a personal blog for him ( ? )
This reminds me of a podcast I listened to recently about creativity. Maybe its not about the idiomatic question of whether classes are good or bad but more about the act of placing the limitation that helps drive the masterpiece?
This reminds me of a first year engineering philosophy course I took where the prof spent a good chunk of it trying to tell us there is no such thing as 100% objective research then proceeding to tell us that our grades were 100% objective after people complained about divergence between course averages according to teaching assistants. :'D
[edit] I was thinking about redirecting to a google image search of cute animals wearing human clothes but after a few weeks of seeing 'this site can't be reached' my habit was successfully broken
Perhaps this will only spur the global do gooders of the world to come up with better (more permanent) solutions for promoting privacy, free speech and innovation.
As a reader of HN I feel like there is already great work being done here (eg/ lets encrypt).
ahem pineapple fund, if you are a real thing, maybe you can put something under EFF's tree for xmas?
The beauty of having an open source solution is smart and rational people from across the political spectrum can work together on something that everyone agrees is a 'correct' voting system.
It sounds to me like most of the criticism's outlined are solvable. Perhaps the people behind the standard should be engaging the framework community more.
I wonder if you think web components (and the problem they set out to solve) is wrong from a fundamental/architectural standpoint?