HNHacker News
TopNewBestAskShowJobs

jimmont

119 karma · joined February 3, 2020

submissionscomments
jimmont··on Four Eras of JavaScript Frameworks
4 is from a decade ago. Perhaps consider what has happened since.
jimmont··on Four Eras of JavaScript Frameworks
Entertaining, inaccurate article. Weak thesis. If this is the industry status quo, it's remarkable how little depth it has.
jimmont··on Will Japan run on ammonia? Major chemical firms want to build the infrastructure
Where and how do you recommend learning more about this? Thanks.
jimmont··on Ask HN: Is Hybrid Working a Ruse?
It's a political, power game. It simply shows lack of trust and regard for our time, or reflects inexperience and inability to manage. Otherwise the situation would speak for itself and the question wouldn't have been asked.
jimmont··on Ask HN: Is Hybrid Working a Ruse?
gave you an upvote to get you that much closer, HN is a product from a time before the term UX existed, not that it would matter
jimmont··on Unit Testing is Overrated (2020)
the testing pyramid is worth knowing about; unit tests double code size and maintenance cost for the unit; I've found unit tests only fit long-lived code and coverage doesn't generally correlate with reliability of product performance; black box end to end testing at the interface level for the general scenarios does correlate with reliability, for those scenarios; writing tests that properly separate concerns in this way seems to make it easier to write and maintain tests, and the product
jimmont··on We use GitHub Actions to build GitHub
Which ones?
jimmont··on My attempted cult recruitment
What a remarkably unhealthy perspective. Yet engaged in communication here. My first thought was you must be American, but that could just as easily be quite a number of places and cultures across continents. In Israel personal boundaries are quite different and it's common to engage those around you in conversation. I wouldn't correlate mental stability with social norms--frankly I associate health with social engagement, so the opposite.
jimmont··on Dirty Pipe Explained
Thanks for this reference, I found the timeline interesting, especially the initial report in 2021, then the one month sequence and timeframe in 2022.
jimmont··on Shoelace: A Web Component Kit
This is simply a reflection of the depth of design (visual and user experience). I'm saying contemporary UX and UI mostly ignore, or are ignorant of, the platform being used and its features. That's not necessarily the case with shoelace, the loading is simply a design decision made to look nice and I presume not much more. The shoelace component system is ok. It reflects a lot of work applicable to what has been possible and borrows from what has been possible the past few years. I find it interesting to see the details in systems and approach and would avoid using this product myself. I haven't reviewed it enough to get past the general impression that it's too complex to be worth the investment and has some weaknesses in the system and technical design. If I were doing a masters in visual communications it would definitely be worth a look, or if I wanted to lead a new project like it as well--to take the understanding of the problems and approaches.
jimmont··on Shoelace: A Web Component Kit
This is like asking if html elements are SEO friendly. It depends how they're implemented. Google handles javascript now, if that's the salient detail.
jimmont··on Study Tips from Richard Feynman
These accommodating adjustments are appropriate in many contexts.
jimmont··on Audi owner finds basic HVAC function paywalled after pressing button
Has anyone priced the map updates? A friend told me how he updated firmware to change various things, learning in the process it's possible to adjust the turn signal (interval, etc). Fairly entertaining stuff.
jimmont··on Employees are returning to the office to sit on zoom calls
this outcome can exist remotely, it simply requires effort and maintenance; the gains from working remote are the same scenario, just different context; I haven't figured out yet the specifics of what works because it hasn't been a priority, and what components of it are the quirky part and what are the catalysts for the same outcome (yet); my flaw is thinking outside the box, which managers and companies don't optimize for; in fact in exemplary situations where I led efforts that gained many times the cost of all my work for many years (millions in USD) they didn't notice or care, which I find hard to understand about US corporate and cultural norms; I'm sure there's a relationship between these things, I just haven't sorted it out.
jimmont··on I wasted $40k on a fantastic startup idea (2020)
> By not understanding the environment you’re not going to be able to understand the Problem which means your Solution will probably fail.

Yes it boils down to politics. Having built a platform for accelerating routine histocompatibility analysis (providing customers a profit from the start) I got to see this firsthand. Risk aversion across the industry, small armies of established technicians working manually, administrators making purchasing decisions with no understanding of the science or impact, the myopic insular bent of academics, the massive gap between healthcare and modern technology. One could pay labs to save time, improve outcomes while reducing risk and they still wouldn't use your product if it doesn't map onto their political priorities.

jimmont··on Deno Is Webby
Deno is the best thing to happen in web middleware, potentially over its entire history. It's like someone solved those problems over many years, took a break, then started from scratch to do it properly.
jimmont··on Diary of a first-time on-call engineer
orgs that have on-call engineers that aren't part of the operations and infrastructure come with all the other associated management and strategy problems; seeing how effective orgs work, how they test, how they release, how they manage faults, how they grow and what instruments and strategy are successful is so simple and straightforward it's mind blowing the general pattern of on-call exists; until you see the people making those decisions then the strangeness becomes how did that person end up in their decision making role given how inconceivably misguided all their strategic comments becomes. I once asked the head of engineering how to get teams to work together and he didn't have an answer--and he also had on-call. It's really strange working in technology, you'd think there were actually intelligent people leading this space. Instead it's more a simile to religion, politics.
jimmont··on Building a web app with no framework
The web is the framework, documented at https://developer.mozilla.org/docs/Web it's odd seeing comments related to a lack of browser lifecycle management, encapsulation, basically everything core to the notion of frameworks is provided by the platform these days (across all contemporary browsers) https://developer.mozilla.org/docs/Web/Web_Components/Using_...
jimmont··on Building a web app with no framework
here are a few resources: video survey with a lot of nuance, especially relative to React: https://youtu.be/9FB0GSOAESo?list=PLNM_ABHoF7B0qDu0GI09eCXim...

https://developers.google.com/web/fundamentals/web-component...

https://developer.mozilla.org/en-US/docs/Web/Web_Components

https://lit.dev/docs/#next-steps https://lit.dev/docs/composition/overview/ https://lit.dev/docs/components/overview/

generally I do this: * make components that take responsibility for a bucket of concerns: like the app (track the app state--user, etc); then views (generic pages, more complex main-section things, etc); then more granular composable stuff like a highly specialized button (arbitrary example); * communicate state changes up via events, for global or highly generalized coordination between anything just handle that on the window/self (setup/undo on the component lifecycle methods); send/intercept/capture these messages on the event.detail (use composition and bubbling); * stick to first-principles: KISS, YAGNI; don't over-engineer your stuff, use encapsulation, if you don't need a shadowRoot it's not required, or use slotting..., use global styles where that's appropriate, use shadow encapsulation of styles where that's separately appropriate--keep those concerns separate and use common sense about appropriate separation of concerns; * don't automate or use external libraries or anything fancy unless it has a clear self-apparent business case (for my work or the customer or the business); forget all the assumptions of the frontend community--it's mostly noise

an example, it's very rough and I'm working through a starting point for myself: https://github.com/sourdough/starter

jimmont··on Building a web app with no framework
I did back in 2016-17 when v1 web component support came to Chrome. Overall it's an approachable problem and takes quite a bit of time and attention to detail. The two significant problems I found are depth of familiarity with Web APIs and the nuance and attention to detail for complete problem solving. The time cost in doing this isn't trivial so it competes with delivering a product on short timelines--which means your MVP delivery might be slower and you might spend less time on design (I have a design background). The most significant secondary observation I've made is how entrenched the community is in these proprietary solutions, and the cost associated with their maintenance over time. The time cost of knowledge and productivity for React, Vue and Angular are similar so in the end the long life of native web api knowledge is the better investment. Since making the product (it automated antibody analysis for routine compatibility profiling in transplant medicine) Lit (LitElement, lit-html) became available and they're so lightweight I use these as often as the native web component mix. It's probably more accurate to say I use them equally because that's just how it works.
jimmont··on SPAs Were a Mistake
Don't don't do what I would do. The mistake is forgetting first principles. You don't do something good by focusing on what not to do (like don't be evil). Focus on what to do: KISS, YAGNI, etc.. even DRY is a far lower priority. Software, especially frontend and web are rampant with problems from operating as an echo chamber. Just consider what Ryan did with Deno and had to say criticizing his first project. Yet folks are still wildly supportive of the older technical decisions and go to great lengths to preserve those same mistakes.
jimmont··on Solid.js feels like what I always wanted React to be
What is your point--or question? Form elements are complex. I'm not familiar with cypress. Puppeteer has worked fine for my needs. If the thesis is simply that using web components is a chore, well, welcome to frontend work. It has always been a chore in one way or another. Web components are the first time I can say--for my own professional experience--it was less so than previously. Generally a superior experience to all of: React, Angular, Backbone, jQuery, etc. Maybe you just need to hire me? I couldn't say without more detail.
jimmont··on Solid.js feels like what I always wanted React to be
Only a clarifying point to add about Lit: tagged templates provide templating and have native support, all Lit does is provide API extensions for reactivity, ie state management. So when a portion of a template is associated with an object, only that part is updated due to how the libraries work. And this is fundamentally all the it provides (unless I've misunderstood something). Lit-html provides functional state+template views while LitElement provides the OO/class oriented lifecycle approach--collectively now rebranded as "Lit". https://lit.dev/ Please call out corrections as needed.
jimmont··on Solid.js feels like what I always wanted React to be
I only have this generalized experience to respond with (at the moment): For the private project i work on full-time, the few dependencies related to ING and Lion were the most problematic and the first to get ripped out. I have no idea about the specifics of your dependency, and will not review the work you're mentioning in detail. However, ING, based on my limited experience, is nothing to base any assumptions on. Based on my limited experience, ING and Lion appear to be distinctly inferior examples of work done with Lit and web components. That was my first and last time working with anything Lion and ING related.
jimmont··on Solid.js feels like what I always wanted React to be
I didn't find the word "think" in the article. Did you mean "feels like this looks cooler"? Feeling does appear to be the prevailing way decisions are made and put forward in the community. I think that's a problem. And one that won't be going away anytime soon.
jimmont··on Solid.js feels like what I always wanted React to be
Big call? I suppose there's a point where having done enough work in projects affords some perspective. Whenever anyone gets the feeling to do something else the docs will probably be there, as they were the past few years.
jimmont··on Solid.js feels like what I always wanted React to be
This is about "feels like" and me too--the little newsletter popup and lack of substance shows this. React became obsolete over the past few years as browsers increasingly adopted the mix of web components features (eg componentDidMount vs connectedCallback). Just using React, and the explanations for why a technology is and isn't used in an organization speaks to the level of practical knowledge and detritus in projects. That products survive this long with React illuminates how resistant the community is to... reading and doing work in the easiest, pragmatic way possible. Like why bother writing an article like this?
jimmont··on Open source alternatives to popular SaaS products
Communications from these platforms look so absolutely unprofessional. Having gone through a dialog with a couple familiar names now publicly traded it's strange watching the amateur hour that is this train wreck of dated, half-baked tooling. You can't tell if you're submitting personal, sensitive info to the business entity or if it's some phishing scheme.
jimmont··on Why you should switch to Brave from Google Chrome
Useful, accurate article. Sometime in 2020 I started using Brave as my default browser on the suggestion of a more-privacy-concerned engineer and it definitely saves a lot of resources over Chrome. I was tethering via my phone most of the time and definitely recommend it generally based on the experience. Brave search I haven't found to be as effective as the article suggests, but can take another look and will be curious to see how that effort goes--it seems promising.
jimmont··on State of JavaScript 2021
Deno missed the library list (it includes an extensive standard library) and I'm glad to see it in included in the runtimes and mention of new things. I just finished moving an app from Nodejs+npm to it and am finding work is quite a bit easier. Initially I'd thought it was completely missing.
← PreviousPage 2 of 5Next →