XLcommerce

8 ms·

1.
by XLcommerce 14y ago
This is the route I've gone. The core CRUD part of the app is PHP, and the real-time chat and document collaboration aspect of my app is node. Works beautifully. I've had so much fun working with node for the last few days.
2.
by XLcommerce 14y ago
could you give more details of your diet please?
3.
by XLcommerce 14y ago
It's a shame you don't have a reproducible test for the rendering issue in Chrome. Until you can reproduce it there's really no telling what is going on. Do you have any links to similar issues already reported? I'd be curious to read up on
4.
by XLcommerce 14y ago
Seems like about half the issues you've mentioned relate to differences in syntax/behaviour. This is to be expected. That is what vendor prefixes are for. They are a known (and necessary) evil. Would you prefer to allow the design by commit
5.
by XLcommerce 14y ago
No offence taken. Sounds like burnout was the wrong term to use. Maybe I staved off actual burnout from developing later on by taking this time off. Either way some manual labour felt good :)
6.
by XLcommerce 14y ago
I was starting to feel some burnout a week ago after a couple of months of 10+ hour days 6 days a week. Refurbishing my roof worked wonders for me. Spending 3 days pressure cleaning, replacing tiles and painting did wonders for me. Obviousl
7.
by XLcommerce 14y ago
It reads like a newspaper. You read one column at a time. No hopping between columns.
8.
by XLcommerce 14y ago
A few people have mentioned information density as being important. I've got the 'Stylish' chrome extension installed with a userstyle for hn which looks like this: table > tbody > tr:nth-child(3) > td{-webkit-column-count: 2; }
9.
by XLcommerce 14y ago
How was the original author acting entitled? He's merely saying that instead of insulting his intelligence just give him some screenshots and info about your app in the noscript. If your app is worth it he'll flick the js switch to the on p
10.
by XLcommerce 14y ago
That's an important question to answer. Creating a site that works sans js then layering on js is great, but it does entail duplication of effort, a larger testing burden etc. It's important to work out if the ROI for going the extra mile m
11.
by XLcommerce 14y ago
the problem isn't whether ie10 is good or not. It's that microsoft's update schedule runs at a glacial pace compared to chrome and firefox, both of which are on a 6 week(!!) rolling release schedule. Compare that to IE where literally years
12.
by XLcommerce 14y ago
I've not used the Rails ORM so I can't comment on how good it is or how easy it is to debug queries (peer behind the magic). *The ORM automates things like tersely expressing the object associations I've built, leaving room for fewer syntax
13.
by XLcommerce 14y ago
Yeah, said much better than I could. I don't regret any of the time spent with these frameworks because it really broadens your horizons and makes you think in new ways. Lots of the techniques I've seen now make regular appearances in the v
14.
by XLcommerce 14y ago
Such a great question. I spent a lot of time working with ExtJS having been lured in by all those great, straight out of the box components which had their own healthy dose of added magic. Fast forward a year or two and suddenly when I need
15.
by XLcommerce 14y ago
Awesome! Must be such an amazing feeling to receive that first payment. I'm about a month away from my first launch and I'm terrified of launching and then hearing.... crickets. So congrats to you! Had a look at the product. Looks v.solid.
16.
by XLcommerce 14y ago
Seems win-win to simply use chromeframe. Given this is a web app which presumably customers are already invested in using (since they're paying for it), requiring a 60s one-time install seems like the best course of action for everyone invo
17.
by XLcommerce 14y ago
Supporting IE means taking on board a technical debt that will follow you for the life of the project. There are lots of things that can be accomplished in ie6 but then you need to consider performance. If you're building an app that means
18.
by XLcommerce 14y ago
Choosing not to develop for IE makes perfect sense if you're building an app. Here's my own little anecdote: In the last 4 months or so I've written around 10k loc for a JS app. and probably 3x that many lines of combines CSS and HTML. Numb
19.
by XLcommerce 15y ago
Yeah that's a fair enough comment. The truth is that I'm probably using more like 2% of the program. I think for someone like me the perfect balance of features/performance was at about cs2/cs3 maybe even cs1, I cant remember. So I most lik
20.
by XLcommerce 15y ago
hehe touché
21.
by XLcommerce 15y ago
yeah I'm really starting to realise that I'm using the wrong tool for the job. I only use it for web design, so from my pov all the photo features are bloat.
22.
by XLcommerce 15y ago
Photoshop is a classic example of bloatware taken to the extreme. I'm running CS5 and routinely run out of RAM with just a few modest files open. It's ridiculous. I'm going back to CS3 as soon as I find some time to upgrade
23.
by XLcommerce 15y ago
I agree with you that browser support sucks. the technology itself is really cool though. Scriptable, heirarchy based vectors. What's not to like?
24.
by XLcommerce 15y ago
painfully fake. i'm surprised that there is even any discussion as the whether it is fake. putting aside the breaking of the laws of physics the actual cgi shots are c-grade at best. Look a the linked wired video between 0:35 - 0:40 the cgi
25.
by XLcommerce 15y ago
I don't think you've used svg before. It definitely does not suck.
26.
by XLcommerce 15y ago
hehe just came back to check my comment history... dude u really created what 3.. 4? different accounts to reply to my messages?? Lol i really got under your skin. you are familiar with this right? http://www.flickr.com/photos/villagemembe
27.
by XLcommerce 15y ago
I've heard it described as the post-employment era. Scary consequences if you let your imagination run with the possibilities. Some interesting reading: http://www.wfs.org/content/postemployment-economy http://www.impactlab.net/2011/10/1
28.
by XLcommerce 15y ago
caused clueless "developers" (along with library authors) to beg for "native" selectors. ahh now I get it. you're one of those guys. you're just smarter than everyone else right? good luck with that.
29.
by XLcommerce 15y ago
Using "CSS selectors" to traverse a tree of nodes is utterly stupid. Clearly your opinions differ from the majority of the web community. Why do you think we now have document.querySelectorAll? Have a look at the mdn article: https://dev
30.
by XLcommerce 15y ago
you're kidding me right? Obviously you filter your queries to the closest node. Are you testing your code on ie6 running on a 486? Even a 486 could parse out a handful of nodes from a dom sub tree in max double digit milliseconds. Those 'Fr

More ›