I couldn't agree more. While it may not be a "show hn" project, the developer may still be a member of the hn community. If one is going to criticise the project, they should at least do so constructively so they can improve it. I don't think any of us would really want snarky remarks as the feedback to something we poured our free time in and shared with the community to garner feedback.
Treat other developers in the same way we would want to be treated if in a similar position :)
Swing contains a fairly sophisticated rich text editor component that can easily server as the basis for a word processor for many cases.
It has nice style support.
I did a neat little screenplay-writing program with it one weekend...I simply created styles that matched to common screenplay formats (like dialog, scene descriptions, etc), assigned hotkeys to the styles, then wrote a little smart method to figure out the next probable style when you hit the return key.
I second that. The offering looks like a mish mash and I cannot even imagine how usable it is. I don't know how an alpha version qualifies as recreated MS Office in 30 days.
What they should have done was to start with a single product like you said work on the essential features, get feedback and cruft out all the additional advanced functionality that the MS Office version has so you'd have a cleaner, leaner offering.
Although sometimes, at the end of the day, the issue isn't so much the software being the perfect tool but how compatible is the tool with existing processes. We use MS Office on the business side and OpenOffice on the engineering side - so much pain when sending documents across the two divisions with documents not looking the same.
Want to build the perfect tool, the better alternative? That's great, but why don't you start with a single product, say, a word processor, or a spreadsheet?
Or take a step back, look at the ways people need to collect, manipulate and share information today, and consider whether a new application that fits into an established category like “word processor” or “spreadsheet” is still a good tool in the first place.
I don’t know what will eventually displace MS Office as the universal toolbox for these things, but somehow I doubt it will look very much like classical office applications at all.
That's the Writely model: Create a "clone" of MSWord with some advantages (online, simultaneous editing, ...) and some disadvantages (not every feature under the sun), and make this one product very useful (and get acquired by Google).
As much as I admire this guy's effort - and his intentions. This is a tool of the past. And he based it on NetBeans?
You know, I spend 8 hours every day developing in NetBeans. It's OK to work in, and you can create cool applications with it, mostly Java EE apps in my case. But basing something on top of such a heavy and bug ridden platform is not a viable long term approach.
And why call it "The Open Source Java Office Suite"? Users do not care whether it's Java or C# or what not, as long as it's better than current offerings out there.
I could go on. Sorry - I'm not excited by this, but perhaps someone else is?
> And why call it "The Open Source Java Office Suite"? Users do not care whether it's Java or C# or what not, as long as it's better than current offerings out there.
It seems to be a trend with developers sometimes to get so involved in what they make that they forget who their target audience is (I would guess in this case he wants more than developers to use it). If his only fault in target audience usability is the naming, then he's doing pretty well (don't know if it is or not yet and usability is subjective). Either way, still a great learning experience taking on a project like this and I don't think I would judge it past "proof of concept" so far.
I have been writing a framework that supports building what I consider to be the Minimum Viable Product of any successful social app. (One that will go on to success in this new environment of 2013, mobile phones etc.) We took care of everything, from user signup, to realtime updates and offline notifications, to access controls, roles, contacts, invitations, and even auto-scaling in case you get to millions of users. And it took me two years and help from two additional developers.
I guess that's a huge amount of effort for the number of people, but overall it's something that a large company like Google or Facebook already built in-house.
Just goes to show some problems require more than others to solve. And also, by leveraging existing libraries, you can more quickly build an MVP that may not scale but can show off the capabilities.
That's different. Our "product" is a framework that repeatably lets apps become viral and get millions of users, through mobile phone invitations instead of facebook. Bsaically it turns your mobile phone into a social platform, with the address book playing the role of the friend list.
I guess it comes down to what you understand "viable" to mean. Because if:
1. our app couldn't work on all mobile platforms => you wouldn't be able to invite many of your contacts, losing a lot of virality that could make the difference (http://luckyapps.com/blog/?p=12)
2. we didn't produce native apps, e.g. with phonegap => lack of integration with addressbook would reduce virality and convenience for the user
3. our app didn't have a one-step invite process => people would get tired of jumping through hoops and virality would suffer
4. our app didn't have realtime updates in chat => people would have to keep refreshing the page on their mobile phone and not get rewarded for engaging with the app
5. our app didn't have offline notifications => engagement would suffer, as the app wouldn't be able to notify people of relevant things via transactional notifications
6. we didn't have ways to manage notifications => people might get annoyed they are getting too many notifications ... yes, this one we could have done later
7. we didn't have ways to manage privacy / access => then everything would have to be public, making many people concerned ... yes, this one we could have done later
8. didn't have auto scaling where we split shards that get too hot and bring up more machines => if all the virality and engagement was as high as we expect, then our machines would quickly crash and we would lose ALL our momentum.
So we decided to invest in 1-8 up front before launching. We have an unusual strategy, having built a distributed platform with all the features of a social network that puts the power into your hands, and works with realtime and mobile ... and having a completely distributed team that is based throughout Russia and Ukraine. We are now in a position to launch many viral apps very efficiently and manage all their common issues on one platform.
PS: We didn't just sit on our hands while building this framework. We already released two apps that have 250,000 monthly active users, so that is why we were worried about growing exponentially from there, once we made them "social".
PPS: Wow, this was a long post. I hope it was informative.
Check out the cross-platform LyX. It's an outstanding front end for working with TeX, on many platforms (Windows, Mac, Linux). I really enjoy using it. On many Linux distros you'll just need to install the lyx packages.
LyX gets you out of the presentation frame of mind, and straight into your content. Recent versions do a great job of integrating vector graphics (like SVG from Inkscape). PDF output looks fantastic.
Are you referring to the same Apple Pages that hasn't been properly updated since 2009 (excepted for iCloud integration, yay!). Also, in my opinion, Pages is a usability nightmare (only opening the inspector makes me want to cry :D)
I am looking for something smart. That will have a distraction free editing, markdown support, pagination and all the good stuff. Some small git integration. So my girlfriend can do version control on her works. I really miss that.
If you're on anything, google documents is excellent - and you don't have to back up, you always have your documents, they are available mobile, and best of all, collaboration. I'd never go back to an installed word processor. The net benefits (no pun intended) are just too compelling.