Earlier quoted context omitted.
I’m glad this is working for him, but it’s only been three months. The most important thing Word gets me is an excuse. If someone sends me a Word doc and I open it in Word and something is screwed up, I can say “oh, um, maybe something is wrong on your end.” If I’m using anything else—LibreOffice, Pages, Google Docs, anything—then there’s a possibility that it’s the software’s fault. I can’t be messing around with th…
I'm principally a transactional attorney. The one piece of software that keeps me tied to Windows in addition to Word is Workshare Compare. To my astonishment, even after jacking prices after the recent acquisition by Litera, there is literally no substitute for elegantly and cleanly preparing redlines. This cannot be that difficult. Somebody build a competitor!
Running a Law Firm on Linux
231–240 of 263 posts
Re: Running a Law Firm on Linux
#232Earlier quoted context omitted.
This a weird argument; It's like asking why graphic designers use Photoshop instead of coming up with their own image manipulation application. Word is literally the top-tier application for developing documents and lawyers are using it for exactly what it's designed for.
If graphic designers were collaboratively editing images where change management was critical and every pixel had to be manually inserted to generate a very specific meaning I suspect that they would come up with their own format and associated applications.
Re: Running a Law Firm on Linux
#233Law firms often charge by the hour, right? If my law firm switches to Linux, would they bill me more hours if they run into technical issues?
OH YES THEY WOULD. Nothing like paying a $500/hr lawyer for debugging a Word table (how can I center text in a table?) or an autonumbered nested list. Not to mention trying to figure out why a whole section doesn't appear in the ToC because "Update Table of Contents" only changed page numbers (Styles weren't used for that section).
Re: Running a Law Firm on Linux
#234has anyone here used decoded.legal? They do appear from time to time in articles on theregister. Would be tempted to try their services at some point.
Re: Running a Law Firm on Linux
#235Earlier quoted context omitted.
Lawyers writing documents is much less like factory composing data than you seem to think. They very much treat it like writing and editing any other kind of written composition. Heck, a lot of lawyers actually dictate their work instead of typing themselves.
It actually reminds me of plumbing more than anything else, especially appellate briefs. Unless and until you get the hang of dictating, your documents will be twice as long. And who is going to do this typing? Someone in Bangalore? Good luck with that.
Dictation is not an obscure thing in law offices.
Re: Running a Law Firm on Linux
#236Also a lawyer here, I think the biggest hurdle is MS Word. MS word is the defacto IDE of the law world. We spend most of our time in Word. The drafting of documents won't be a problem with libre office. You can send a PDF to the client. But working with other lawyers/parties could be a challenge. I am not certain how Libreoffice could handle a 500 page memo being worked by 50+ people including thousands of track chan…
As a scientist I'm really tempted to ask: Why not latex and track changes? I already know the answer of course, but it's interesting how much of this type of thing is 'cultural' and institutional momentum.
Re: Running a Law Firm on Linux
#237Also a lawyer here, I think the biggest hurdle is MS Word. MS word is the defacto IDE of the law world. We spend most of our time in Word. The drafting of documents won't be a problem with libre office. You can send a PDF to the client. But working with other lawyers/parties could be a challenge. I am not certain how Libreoffice could handle a 500 page memo being worked by 50+ people including thousands of track chan…
if only lawyers used git, sigh. fighting word is almost like fighting the system itself - some courts require filing in .doc!
For most document versioning and redlining needs, only the basic concepts are needed and correspond to common concepts: new document (init), save document (eh... commit? push?), save as (branch), open for editing (clone?), open for read-only (fetch?), and compare to other document (diff). Tracking and merging changes should be separate from those overall document actions, but are similarly congruent with git concepts. Again, the problem is presentation.
I want to jump on the hate bandwagon for MS Word, but in all honesty as long as you stay clear of "the cloud" and deal with documents locally and/or via email, it does all of these things quite well visually. It's fairly intuitive in its track changes interface. Virtually all of the complaints about numbering and formatting and pagination are due to user error -- which admittedly is often because of UI obscurity. The main thing missing is better and more visible built-in version control, but MS had SharePoint already queued up for that purpose so it makes business sense to try vendor lock in and upsell on that.
My only real pain points with Word are the severely limited reference manager, dismal attempts at a templating engine, and the crippled mail merge functionality. All of these can be scripted away or fixed with shady extensions, at the cost of IT freaking out about "dangerous macros".
Word 365 on the other hand... burn it in the fires of the hells from which it spawned.
Re: Running a Law Firm on Linux
#238Earlier quoted context omitted.
I don't think you understand how enterprise managed windows machines work. They come full of very intrusive tooling and usually custom built windows images. Dell on the other hand - on of the largest suppliers of enterprise PCs - offers no warranties for any custom image Windows machines even if they use Dell official driver bundles. I once came into a Windows Enterprise shop with the same arrogance and thought I cou…
I don't directly deal with Windows desktops but am directly responsible for an estate which includes north of 40k Windows Server systems. As a result, I do have a pretty solid handle on managing Windows at scale (at least in the datacenter). We don't see a BSOD a week across that entire estate, let alone a single system. BSODs are a sign that something is SERIOUSLY WRONG. Usually, failing hardware or sometimes shitty…
Re: Running a Law Firm on Linux
#239Earlier quoted context omitted.
It happens all the time. In the middle of medical malpractice cases, divorce cases, murder cases - a virus update, an acrobat update, an email notification, etc. Everybody deals.
My favorite was at a hearing where opposing counsel had printed off that morning a copy of a letter he felt was dispositive. Word automatically "update(d) fields" and so the six-month old letter bore the date of the hearing. The judge didn't understand the concept and said the letter could not possibly be accurate; what other content was changed? His motion was denied. Thank you, Word!
Re: Running a Law Firm on Linux
#240Why would law firms want to exchange documents in a dense, opaque format like Microsoft Word anyway? Legal documents are mostly about the actual words, not all the word processing stuff that Word is about. You would think that the legal world would of come up with their own application specific format by now.
You've never worked with a law firm have you (either as a client or internally). Two words: Tracked Changes Everyone knows how Word tracked changes works. Especially lawyers and their clients. Beyond the above. Formatting. Firms will have have substancial know-how in Word formatting. Sure the contract is about the words, but when you present it to the client, it is all nicely formatted in a standardised format.