Live data from Hacker News

Mozilla Brick

brick.mozilla.io

41–50 of 122 posts

Re: Mozilla Brick

#41
post #20

Can I use this client-side? From what I read on the page this seems to be only geared towards a certain server-side-setup with node.js, brewer and stuff.

Yes you can. If you check out http://brick.mozilla.io/v2.0/docs/getting-started - Node and bower are used in order to install the library locally. You can also download the project from Github ( https://github.com/mozbrick/brick ) and just copy-paste the needed files in your project. You can search for them in the 'dist' sub-directory.

Thanks. That might work. But it feels a bit unaccessible. Looking through the code also gives me a strange feeling. Too many dependencies. They should just give you a .js that enables certain functionality and thats it. Like "include brick-flipbox.js and you have flipbox functionality".

Plus most of the demos do not wort (tried in chromium).

I don't believe in this thing.

Re: Mozilla Brick

#43

I looked at this in Chrome and honestly couldn't figure out if the examples were actually working. Also, Stylus seems a curious choice (not because it's bad, just that it's not exactly the frontrunner in the CSS preprocessor race). I'm not even sure why a CSS preprocessor is even necessary, to be honest.

[deleted]

Re: Mozilla Brick

#44
post #37

Earlier quoted context omitted.

yea because it's much better to have closed, restricted app markets (like Apple, Google, Microsoft ones) than web standards.

It's a choice between restricted standards that hinder technology innovation and restricted markets that hinder business. As a technologist I hope that de-facto monopolic legacy poorly-designed technologies (JS and HTML) will give way to new better technologies. I am very happy that at least mobile still gives developers many options - mostly without lame transpilation.

Restricted App Store rules eg. disallowing external web browsers or interpreters hinder technology much more than web standards.

Talk is cheap - would love to see some of yours "not lame" piece of work.

Re: Mozilla Brick

#45
post #14

Earlier quoted context omitted.

I hope the apps market keeps recovering. This will put pressure on dinosaurs like browsers pretending to be an OS.

yea because it's much better to have closed, restricted app markets (like Apple, Google, Microsoft ones) than web standards.

You means the standards where each browser version has its own view of the world, or the standards where the applications get executed behind a HTTP(S) key hole?

Re: Mozilla Brick

#46
Hm... am I correct that the brick-action component is actually their way of setting up a listener, like Backbone's obj.listenTo(anotherObj, 'event', callback)? Well, in that case it's one hell of an overhead, imagine creating an actual DOM element for every single event listener.

Re: Mozilla Brick

#47
For me personally, the challenge UI frameworks like Bootstrap solve is the pure UI. That is, which borders, shadows and spacings to use and such stuff. A thin layer on top of the actual APIs like Mozilla Brick does not seem too useful to me - why bother adding a third party component if it merely wraps the functionality of HTML/CSS? (Although I must admit I haven't used Brick yet.)

Re: Mozilla Brick

#48
post #37

Earlier quoted context omitted.

It's a choice between restricted standards that hinder technology innovation and restricted markets that hinder business. As a technologist I hope that de-facto monopolic legacy poorly-designed technologies (JS and HTML) will give way to new better technologies. I am very happy that at least mobile still gives developers many options - mostly without lame transpilation.

Restricted App Store rules eg. disallowing external web browsers or interpreters hinder technology much more than web standards. Talk is cheap - would love to see some of yours "not lame" piece of work.

E.g. iOS lets me use: Objective C, Swift, C#, F#, Java, Scala. All compiling to lower-level code that is either native to platform or native to the language.

Web lets me use: only JavaScript (that is written manually or transpiled).

Yes I will have to pay extra for some solutions, but I don't mind doing this as opposed to using language that I hate.

http://en.wikipedia.org/wiki/Ad_hominem

Re: Mozilla Brick

#49

Earlier quoted context omitted.

if you include the platform.js file, everything should be supported in the last versions of every browser

Hmm. Something more specific? I assume evergreen browser support means - Chrome, Firefox, Safari, Opera, IE, but which versions. What about mobile OS ?

The whole point of "evergreen browsers" is that the version number doesn't matter.

Re: Mozilla Brick

#50
post #48

Earlier quoted context omitted.

Restricted App Store rules eg. disallowing external web browsers or interpreters hinder technology much more than web standards. Talk is cheap - would love to see some of yours "not lame" piece of work.

E.g. iOS lets me use: Objective C, Swift, C#, F#, Java, Scala. All compiling to lower-level code that is either native to platform or native to the language. Web lets me use: only JavaScript (that is written manually or transpiled). Yes I will have to pay extra for some solutions, but I don't mind doing this as opposed to using language that I hate. http://en.wikipedia.org/wiki/Ad_hominem

> iOS lets me use [...]

And Web Components are bringing innovation (component based app building) to rusty world of web dev which is not restricted to rich western society (Apple).

I stopped ranting on JS - just use lang with good enough IDE like Dartlang (DartEditor or IntelliJ)

PS: previous comment was not "ad persona" - but if you think transpilation is "lame" - you don't know how hard it's to make performant transpiler and how wonderful piece of tech are some of those transpilers

Post reply on HN