Way to edit your post when I was midway through responding :-)
We're relatively unconcerned about our website's (home page) source. Our actual application can be seen at https://www.lucidchart.com/demo. There you'll see a single large Javascript file served from Cloudfront, plus a few third-party-hosted files that we couldn't reasonably CDN (like Google Analytics and some other third-party APIs). There are also three CSS files. One is the bulk of the data (194KB over the wire) which is sent over the CDN. Then there is a separate file for jQuery UI (which will soon be removed) and one that is shared CSS with other parts of our app.
> We're relatively unconcerned about our website's (home page) source. Our actual application can be seen at https://www.lucidchart.com/demo. There you'll see a single large Javascript file served from Cloudfront
We do use sprite sheets for almost all of the icon-sized images (there are hundreds) in the application. And those sprite sheets are big enough to not get inlined in the CSS. The images that do get inlined are generally odd-sized--though I suppose that automatically generated sprite sheets could manage that for us as well.
Exposing CSS is much less of an issue than exposing Javascript; that list was speaking about JS and CSS generally ("why a build process"). The post goes on to describe why CSS specifically is worth paying attention to.
That's a pretty bold (and borderline offensive) statement. You're effectively thumbing your nose at anyone who develops open source projects and even more so, anyone who subscribes to a philosophy of the open-nature of the web.
I think you're taking my tongue-in-cheek reply to a troll a wee bit too seriously :-) We love open source at Lucidchart and employ a lot of people who contribute in meaningful ways to a variety of open-source projects.
That's pretty big talk coming from someone whose site has ~250 !important declarations in their CSS on a single page, and had to use a jQuery plugin to handle cookies (lol). If working there is an "amazing job" then I'm on a pretty awesome level.
Lucidchart is a rapidly growing tech startup looking for great backend software engineers to join us at our headquarters in Utah. At Lucidchart, we build killer graphical web applications requiring highly available, secure and scalable backend services. Talent and ability to learn are more important than years of experience.
You may have seen Lucidchart demoed during the second Google I/O 2012 keynote: http://t.co/sd6GgZvy
We're hiring BACKEND SOFTWARE ENGINEERS. Lucidchart runs with various decoupled services in a Linux environment using Scala, PHP, MongoDB and MySQL. At Lucidchart, your responsibilities would include enhancing existing services, building new services, integrating with 3rd party applications and ensuring services are highly reliable and scalable.
Requirements: * Talent
Recommended experience: * Have built large products / applications * Scala or Java * PHP * MySQL or other relational database * NoSQL databases (MongoDB especially desirable) * Opscode Chef or Puppet * Cloud computing (AWS)
We're also hiring FRONTEND SOFTWARE ENGINEERS. We build killer graphical web applications that push the boundaries of what's possible in the browser. Lucidchart is powered by one of the largest Javascript codebases on the Internet, optimized so that the user experience is indistinguishable from an installed native application. Come help us show the tech world what can be done on the web.
Requirements: * Talent
Recommended experience: * Have built large products / applications * Javascript * Google Closure compiler/library * CSS/HTML/DOM manipulation * jQuery * node.js * Native app development on Android and/or iOS * Facebook APIs
We're also looking for a product manager to help us unify the vision of Lucidchart and our future products, develop relationships with key integration partners, and be sure we always deliver the highest value to our customers.
All applicants email resumes to jobs@lucidchart.com.
Lucidchart is a rapidly growing tech startup looking for great backend software engineers to join us at our headquarters in Utah. At Lucidchart, we build killer graphical web applications requiring highly available, secure and scalable backend services. Talent and ability to learn are more important than years of experience.
You may have seen Lucidchart demoed during the second Google I/O 2012 keynote: http://t.co/sd6GgZvy
We're hiring BACKEND SOFTWARE ENGINEERS. Lucidchart runs with various decoupled services in a Linux environment using Scala, PHP, MongoDB and MySQL. At Lucidchart, your responsibilities would include enhancing existing services, building new services, integrating with 3rd party applications and ensuring services are highly reliable and scalable.
Requirements: * Talent
Recommended experience: * Have built large products / applications * Scala or Java * PHP * MySQL or other relational database * NoSQL databases (MongoDB especially desirable) * Opscode Chef or Puppet * Cloud computing (AWS)
We're also hiring FRONTEND SOFTWARE ENGINEERS. We build killer graphical web applications that push the boundaries of what's possible in the browser. Lucidchart is powered by one of the largest Javascript codebases on the Internet, optimized so that the user experience is indistinguishable from an installed native application. Come help us show the tech world what can be done on the web.
Requirements: * Talent
Recommended experience: * Have built large products / applications * Javascript * Google Closure compiler/library * CSS/HTML/DOM manipulation * jQuery * node.js * Native app development on Android and/or iOS * Facebook APIs
All applicants email resumes to jobs@lucidchart.com.
That's right, these were all done on a Windows 8 machine. We could of course test on Safari 6 on a Mac, but then the numbers wouldn't be directly comparable (since it's different hardware).
I think your article would benefit from making this piont clearer. There's been discussions on HN before about how performance of Apple software on Windows differs greatly compared with performance of Apple software on Apple OSes.
Interestingly, the part that crashed Firefox was one of the simpler tests--typing a bunch of text content in, then resizing and rotating the shapes that contain that text. Firefox didn't give any details as to why it crashed.
The only thing I could even measure that would lead to a crash is memory usage. I just re-ran the test and watched the process's memory usage. It hovered in the 300-400MB range during the first third of the test. Then, during the test I describe, memory usage rocketed to around 1GB, at which point the browser crashed hard.
I'm not sure why Firefox would exhibit this behavior when other browsers don't, but we know a few people at Mozilla (they're customers of ours) so we'll probably reach out.
Why not remove the part of the test that crashed it and post results of the rest of the benchmarks? Those are 3 tests out of 16, I would still like to see how it compares in the other benchmark tests.
Seeing "We're sorry. Firefox had a problem and crashed." as well as its exclusion from the performance summary made it feel like there was a bit of a bias against Firefox, where even in your conclusion it's stated that it performs "quite well" - that sentence does not reflect on the rest of the article at all.
Hi, Lucid CTO here. We've spent a lot of time in the IE profiler, and it never appears that any of our Javascript is consuming much CPU at all. There are a handful of functions, like the one you quoted, that poll frequently on a setInterval. But none of them are doing much more than checking a variable and returning almost every time. It's really bizarre.
Lucidchart is a rapidly growing tech startup looking for great backend software engineers to join us at our headquarters in Utah. At Lucidchart, we build killer graphical web applications requiring highly available, secure and scalable backend services. Talent and ability to learn are more important than years of experience.
You may have seen Lucidchart demoed during the second Google I/O 2012 keynote:
We're hiring BACKEND SOFTWARE ENGINEERS. Lucidchart runs with various decoupled services in a Linux environment using Scala, PHP, MongoDB and MySQL. At Lucidchart, your responsibilities would include enhancing existing services, building new services, integrating with 3rd party applications and ensuring services are highly reliable and scalable.
Requirements: * Talent
Recommended experience: * Have built large products / applications * Scala or Java * PHP * MySQL or other relational database * NoSQL databases (MongoDB especially desirable) * Opscode Chef or Puppet * Cloud computing (AWS)
We're also hiring FRONTEND SOFTWARE ENGINEERS. We build killer graphical web applications that push the boundaries of what's possible in the browser. Lucidchart is powered by one of the largest Javascript codebases on the Internet, optimized so that the user experience is indistinguishable from an installed native application. Come help us show the tech world what can be done on the web.
Requirements: * Talent
Recommended experience: * Have built large products / applications * Javascript * Google Closure compiler/library * CSS/HTML/DOM manipulation * jQuery * node.js * Native app development on Android and/or iOS * Facebook APIs
All applicants email resumes to jobs@lucidchart.com.
We're relatively unconcerned about our website's (home page) source. Our actual application can be seen at https://www.lucidchart.com/demo. There you'll see a single large Javascript file served from Cloudfront, plus a few third-party-hosted files that we couldn't reasonably CDN (like Google Analytics and some other third-party APIs). There are also three CSS files. One is the bulk of the data (194KB over the wire) which is sent over the CDN. Then there is a separate file for jQuery UI (which will soon be removed) and one that is shared CSS with other parts of our app.