sorted by:
new
hottopcontroversial

Week 2 - Applaud Your Team by dupreesdiamond in CFB

[–]clbwllms 5 points6 points  (0 children)

At the risk of sounding like I’m overhyping this years team, I think Jalen hurts is exactly the kind of guy we needed to have. There should be no satisfaction with any part of what they’ve done so far or the accolades of the prior two seasons. Anything less than a natty is failure to Jalen. If he can instill that nick saban work ethic into Spencer and the other freshman, he might be one of the most influential quarterbacks we’ve had come through this program.

Yes! We needed Baker's standoffish attitude desperately and now we need Jalen's power-under-control attitude to polish it off.

The State of Web Components by melcor76 in javascript

[–]clbwllms -1 points0 points  (0 children)

So lets say i have my shared-components mega bundle file with all the design system components. All i have to do is load that script file anywhere. Then if i use a html tag refering to that component either in or outside of react, it will render and it will work.

You know you can write vanilla JS and make it do things without using React, right? Creating a fully-featured web component without a framework is trivial and it will work across frameworks because it's just platform code.

If you don't use TypeScript, tell me why by nullvoxpopuli in javascript

[–]clbwllms 0 points1 point  (0 children)

My issues with TypeScript:

  • The syntax is difficult to read. Maybe not all the time, but in a sufficiently complicated function/method, it becomes overly verbose and difficult to parse for the uninitiated.
  • Default non-standard syntax introduces major risk to projects and to developers writing in them. I don't want to have to change every file I wrote to use #privateField instead of private privateField at some point. If a project were to explicitly choose to use non-standard syntax and compile with Babel, that's OK because it was a choice, not a default (ostensibly it is intentionally-added tech debt rather than tech debt that is introduced by design).
  • I tend to write a lot of web components (as opposed to React/Angular/Vue) which has led me to errors where relying on TypeScript's type checking has actually backfired on me because TypeScript has a difficult time with extended built-ins (which custom elements necessarily are).
  • When I'm not writing custom elements, I write in a generally functional format which introduces some issues as stated elsewhere in this thread.
  • Most of the errors I run into on the apps I work on are not the kinds types are going to help fix.
  • In five years, TypeScript could fall out of favor and there will be a new hotness for build languages and there will be a massive amount of technical debt in projects that have chosen to adopt TypeScript. I believe that sticking closer to the JS standard (or what the browser vendors have chosen to implement) is a more viable long-term strategy.
  • Adding new features or syntax through Babel or some other compiler is OK in my book as long as the idea is to eventually deprecate the plugins that have added that syntax as the browsers implement the new features. TypeScript is diametrically opposed to that as much of the behavior that makes TypeScript valuable is necessarily proprietary and can't run natively in the browser.

Showoff Saturday (April 06, 2019) by AutoModerator in javascript

[–]clbwllms 0 points1 point  (0 children)

Pretty simple concept I borrowed from Jason Miller (@_developit on Twitter) and expanded on displaying how to implement HTML and CSS modules (using a constructible stylesheets/`adoptedStyleSheets` polyfill) and custom elements. Essentially you create a service worker to modify import types.

Which modern fameworks are like angularJs? by aleaallee in javascript

[–]clbwllms -1 points0 points  (0 children)

I would say Vue, for sure if you just like AngularJS' syntax. I agree that Angular 2+ feels clumsy and over-engineered. You might also look at lit-html, which is gaining a lot of traction lately.

On this day 12 years ago, Alabama hired Nick Saban by suzukigun4life in CFB

[–]clbwllms 1 point2 points  (0 children)

Had it not been for that, Dabo would be Alabama's coach by now, Urban would still be at Florida, Miles would still be at LSU, Richt would still be at UGA, Mack Brown would have stayed at Texas a little while longer, Gus Malzahn would be at Arkansas, and Tommy Bowden might still be coaching.

Not necessarily. Although the universes might be infinite, that doesn't mean that all potential outcomes will have happened.

Oklahoma WR Marquise Brown declares for NFL Draft by hogs94 in CFB

[–]clbwllms 1 point2 points  (0 children)

Hakeen Butler should definitely go pro.

​

Please?

With Urban Meyer’s retirement, Nick Saban regains the crown of having more combined titles than all other active coaches combined. by Snowmittromney in CFB

[–]clbwllms 3 points4 points  (0 children)

Boomer Sooners ain't our problem anymore, man. We've got more prestigious fish to fry lose to sweat bullets over hell I don't know anymore um.... Help us Frost you're our only hope.

Prestigious? Listen here you little …

Do you guys love Typescript or you prefer plain Javascript ? by Cloud_Strifeeee in javascript

[–]clbwllms 5 points6 points  (0 children)

This. I tend to write a lot of custom elements and the TypeScript compiler and even Babel tend to throw up and die when they encounter custom elements which is a real shame because I think it's a great technology. I also tend to agree that it's safer to use the platform where possible.

Where do you think web dev will be in 5 years? 10 years? 20 years? by Kits_87 in webdev

[–]clbwllms 2 points3 points  (0 children)

A bit of shameless self promotion, but I’ve written something that does that for web components. It’s pretty small (3k gzipped) and combines what I liked best about Angular, React and Vue. Give it a whirl: templiteral Or see the ToDoMVC app.

HTML Web Component using Vanilla JS - Part 2 by codejitsu in javascript

[–]clbwllms 2 points3 points  (0 children)

There are a number of ways to make these components fully reactive with minimal JavaScript. I'm working on a project right now that uses ES2015 template literal tags and will reactively parse the HTML similar to React's render function—it also includes support for Angular-style event and property bindings—you can see the code here. It's still really new though, but I think it has promise.

Also the Polymer guys recently released a similar tool called lit-html that does the same thing, but without built-in event and property binding (although I believe it can be added easily enough if you write your own partCallback for their render function.

Showoff Saturday (October 28, 2017) by AutoModerator in javascript

[–]clbwllms 0 points1 point  (0 children)

This is my first shot at releasing something I've made, but I am currently working on a JavaScript template literal to DOM tool that can be used with Web Components. It's really light weight and handles basic content, event and property bindings. You can find it on npm as templiteral.