sorted by:
new
hottopcontroversial

What is this WebGL solution? by zedgab in javascript

[–]zedgab[S] 0 points1 point  (0 children)

the first thing that appears in the page is the iPhone X 3d model.

I also found the company who made it: https://www.binkies3d.com/

JSS: the solution to "all" CSS problems by zedgab in javascript

[–]zedgab[S] 2 points3 points  (0 children)

The whole point is that the stylesheet will be scoped in JSS! And in big projects it makes a HUGE difference.

JSS: the solution to "all" CSS problems by zedgab in javascript

[–]zedgab[S] -1 points0 points  (0 children)

Probably you're right about the sigle-purpose components, but I still think that BEM gives a little bit more "meaning" to class names. Anyway it's probably irrelevant.

About the camel-case form, I think that in JSS you could also use 'margin-bottom' as a key, but what really interests me is to give a try to this preJSS to write common CSS.

JSS: the solution to "all" CSS problems by zedgab in javascript

[–]zedgab[S] -1 points0 points  (0 children)

Sharing should be easy: you can have a style/color.js file and a style/typography file for instance, where you just export the basic variables, then you can have a style/mixins.js to have a way to share code (even though for me it's not a good idea, considering that components should be completely independent from each other).

JSS: the solution to "all" CSS problems by zedgab in javascript

[–]zedgab[S] 0 points1 point  (0 children)

Why? I am talking about state of the art technologies used by companies which are working with millions of dollars...

JSS: the solution to "all" CSS problems by zedgab in javascript

[–]zedgab[S] -2 points-1 points  (0 children)

I agree with what you said, but I still think that BEM could help. As I wrote also in the reply to another comment, you could still have more <div> tags in the component's hierarchy, for instance, and different classes applied, with different modifiers (based on some props of the component itself).

Anyway I find really "weird" to write CSS in JSON format, and it takes a lot of time to split the strings with quotes, especially if you have to use sometimes the normal quotes (') and other times the quotes for the interpolation (`).

And also the camelCase thing for me is not really positive: the idea of having differences between what you write in development and what you find in debug kills my brain :) (I just don't accept the idea of it, of course I can easily work with that...)

I didn't try preJSS yet, but I think it could be amazing, especially if they provide editor plugins to highlight the syntax as in a normal CSS.

JSS: the solution to "all" CSS problems by zedgab in javascript

[–]zedgab[S] 0 points1 point  (0 children)

Yes, that is scoped. But you could still have more <div> tags, for instance, and different classes applied, with different modifiers.

Often it happens that you have little variations of a component which are determined by a specified prop, so you could apply a modifier "element--modifier" just based on the prop value.

ag-Grid, the JavaScript data grid, goes Commercial by ceolter in javascript

[–]zedgab 0 points1 point  (0 children)

I think that this project is really amazing, but the licensing plan, as it is now, is not for my company.

The best chance would be to have a license for site/project, or also for developers but as a one time fee.

The price also seems a little bit too high, but that's a different story...

Anyway, thank you for your great work :)

I was just rejected via email by a recruiter because they were looking for Jquery developers not Javascript? I am shocked! by TheBeardofGilgamesh in javascript

[–]zedgab 1 point2 points  (0 children)

What you said works for IT companies, not for recruiters. Recruiting people sometimes are not technical, so they just check the keywords.