its strange that the lockfile was supposed to fix problems with un-repeatable installs, but I had several issues fixed by simply deleting the lock file and re-installing.
392 karma · joined July 24, 2014
its strange that the lockfile was supposed to fix problems with un-repeatable installs, but I had several issues fixed by simply deleting the lock file and re-installing.
I think they hold some responsibility in allowing an obviously malicious package to impersonate popular packages.
I would like to see an official response with action plan. I recall this attack vector being discussed in the aftermath of left-pad.
an unfortunate irony is that the current post on the npm blog is "Securing the npm registry" from 12hrs ago.
I'm bothered by this perception that SPAs inherently provide a better user experience. They certainly can provide a different user experience, but "better" is entirely up to the developers. I'd argue its actually quite hard to create a better UX in an SPA than the simple page based UX metaphor everyone is used to that the browser provides. Netflix is an example of a great UX from an SPA, nba leaguepass is an example of a disaster SPA.
Also there is no inherent speed boost from an SPA. Anything that is slow on the server will still be slow, and its up to the developer to create a good UX for latency. In page driven applications, the browser provides a fairly standard UX for page loading that most people are used to. In SPA apps, the developer needs to roll this themselves. Widgets popping in all over the place at different times, moving things all over the page, is a common UX I see in SPAs that is not good.
mongodb marketing/PR was a problem, advertising a general purpose RDMS alternative without the technology to support it.
users were also a problem, using a technology without understanding the architecture and trade-offs.
to be over critical of "mongodb" though is unproductive. there were a lot good people working on new software to solve hard problems and I'd like that to continue.
lets just not repeat the same mistakes. don't get caught in marketing hype, and carefully evaluate technology decisions.
looks like it got a major facelift since the last time I checked it out. that must of been a lot of work. congrats to the contributors for making that happen, looks more modern.
some tickets are sold via auction, others are offered at a set price to those who win a lottery.
The only difference is that venues + artists can benefit rather than middlemen.
I think VR has the potential to help alleviate some of the market pressures by offering an experience with nearly limitless supply.
unfortunately, I don't think this was always communicated effectively by the explosion of mongodb marketing and hype.
I think the main guilty parties at mongodb were/are in marketing.
technically sophisticated users understood the immaturity of the product and the tradeoffs that came with its architecture.
however it was sometimes marketed as a general purpose data store, or as an alternative to much more mature relational data stores, which was and still is an unfair comparison.
one of the things I love about bootstrap is being able to google "bootstrap <some component>" and get something that works and looks nice.
will these third party components need to be re-written and support multiple bootstrap versions?
There were probably opportunities for the author to architect the system in ways that were better suited to node (given that was the chosen platform), but the architecture choices were not unreasonable by design. These are some good things to consider when architecting a system, and considering node as the platform.
I'm not sure I agree that node is the "perfect for simple CRUD apps" though
node is probably not the best choice for truly CPU bound operations, but you can sometimes get by using the native cluster module to spread work over multiple cores.
the green screen app was highly optimized for efficient and accurate data entry without use of a mouse. The modern alternative looked better, but a large portion of the functionality was much less efficient in comparison.
the only redeeming factor of the new application, was it allowed much of the manual data entry to be automated. This however required considerable time, technical knowledge, and industry contacts to develop and implement, which not all organizational users possessed.
It took about 2 months before the storm finally ended.
It became comical how many responders to the email chastised the original sender for "HIPAA violations" using Reply-All thereby inadvertently committing the same infraction themselves because the original email was included at the bottom of the reply.
Also, several times, after 2-3 days of quiet, someone would come back from vacation and reply-all with "I think you sent this to the wrong person", thereby starting the storm all over again.
The company of the original sender seemed powerless to stop it, but I always wondered if they could have just disabled/deleted that group-email mailing list.
With both Xamarin and React Native there was a honeymoon period where everything seemed so easy and great. But at some point I always hit a problem where there was limited documentation, or unsupported features, and that really hurt my productivity and motivation.
The learning curve for Swift/ObjC always seemed much higher, with a lot more upfront investment required before I could make anything resembling a functional app. The iOS layout system in particular was an obstacle, as well as managing the tooling and dev environments.
If I had a free 6 months, I would just learn full native, but keep an eye on React Native. The dev experience in React Native is unparalleled, and it seems easy to drop down to native code (assuming you know it). Also the ability to easily contribute back to the community with NPM and react-native "link", makes me hopeful limitations will quickly be erased.
You will learn programming as you go, and gradually find a language or framework you like.
If you want want to make games, but you pick up Python 101, you may get bored and move on, because its not what you are interested in. I recommend physical books for beginners. Look for books like "Programming [X] Games for Beginners."
My first real desktop application written in VB .Net has been used once a month for 6 years, and is still going strong, even after I've left the company.
async helps, but when doing a series of operations with dependencies and shared data between steps it can lead to headaches. It took me quite a bit of time before I could think about these operations in a way that was a better fit for an event driven model, and once my mind set changed, things felt simpler.
i've had success recently moving complicated multiple step operations into their own functions. If you follow the callback/error conventions this can be much easier to debug, and you can add your own error handling at each step.