zerkten

This the first thing I look for to establish the credibility of any site, app, or service. It's marginally OK to link to a LinkedIn page, but you have to populate it with credible information. Seeing 0 employees is a huge warning that you should not use the service. This causes me to look harder to understand why this information is obscured.

This is probably boosting metrics so removing it would put them in the sights of management whether it's intentional, or not.

It has been OK for my needs, but I think you are best getting the KVM and returning if it doesn't meet your needs. I'd probably be more concerned if this was for my photography or gaming machine. For a work setup it has been fine for me.

I was looking at this as an upgrade pick and don't have any re-arrangement with my TESmart (TES-HDK0402A1U-USBK). What monitor(s) do you have?

I have a TESmart (TES-HDK0402A1U-USBK) from https://www.amazon.com/gp/product/B08259QL5J/ref=ppx_yo_dt_b... which works fine in this regard. This was probably the 4th DisplayPort KVM I tried due to keyboard issues with the others.

I /think/ this is related to the EDID support or configuration.

What I do know is that you need specific EDID support when using a DisplayPort KVM because that switches the computer away on a regular basis. If you have multiple screens and a single screen KVM (fairly common) it will do the re-arrangement that you've experienced. With EDID support it keeps both output alive resulting in no re-arrangement.

EDIT: It seems the correct term may be "EDID emulation".

It's like this right now on my phone.

Can you share how you are hosting it, photo library file types or size, and what the performance is like? I'm always skeptical of stated requirements and what other people are prepared to put up with.

I've got an older Synology NAS that currently stores my 250GB photo library with a lot of RAWs. While it can run docker I'm not going to attempt to run it there. I'm wondering if a VM on my 10700k is going to be sufficient for great performance, or if handing over the complete machine is going to be necessary. I'm happy adding more NVMe 3.0 drives for storage.

I'm also curious how version upgrades have been for you. I want to get out of the ops business but I feel like I'm going to be dragged in.

At the very least, Twitter has an A/B test going on iOS which switches you back to the For You tab aggressively. It's as aggressive as switching to another app like email for less than a minute and you'll see a jarring switch as the app shifts back to For You tab.

I suspect that's their point, or maybe that of their client. Following the footer you find that it's built by a company that focuses on MVPs:

"A small team of high-skilled product developers has created and launched mini-startups for the last 5 years. We will build and help to validate your product idea in 30 days."

Is there a relationship between the application of product management "techniques" and the outcomes for many of these sites? It seems that many of these sites hit this wall when they get acquired. It feels like they start experimenting incoherently with things that don't align with the vision, or even the goals of the acquirer.

My personal theory is that this stems from many disjointed experiments where the experimentation is viewed as being more important than anything else. Their mission is to deliver revenue, or some other metric, that isn't visible to users, so perhaps they do achieve their goals.

I've wanted this when the primary requirement was a WYSIWYG editing experience acceptable to business users. Neither HTML nor Markdown were acceptable and while it's perhaps more accepted today, there are still huge audiences which won't touch anything looking like code. The options available generated terrible HTML on the backend that wouldn't roundtrip or resulted in problems when the overall site design was changed. I'm completely onboard with your feelings as a technical person.

Using Markdown as the storage format solved the problem because it is consistent and templates can easily be updated to support design updates. The problem is now finding a WYSIWYG editor that supports Markdown. I'm glad there is more going on this space, but StackOverflow helped me a lot with https://editor.stackoverflow.design/.

>> But this is NOT a company being sold! And not even a division or a product sold. It’s not a merger or acquisition. It is, what you described as this: “two standing independent companies exchanging personal data.”

This is just semantics on your part. Whether it's a company being sold, a division, or only a product, then reasonable companies will consider the data handling in a similar way with multiple gap analyses to mitigate concerns. Context is going to dictate what happens. Lesser companies will not consider this heavily and you can end up with the data being more of the value for the transaction. Whether we like it, or not, we are left to trust that these companies will make efforts to enact good policies and follow them.

What I'd expect to happen here is that Google and Squarespace will familiarize themselves with the posture on both sides and Google will want the standards to at least be maintained to a level which removes liability to them. They are very aware of the scrutiny and a big player here so they can force the acquirer to step up to a certain degree.

I don't know enough about Squarespace's security, or complete business model, but they'll be trying to work out what gaps they may need to fill. Google may have clauses that require that this data can't be co-mingled, or must be handled in specific ways for certain countries. The actual handling and what is communicated can take some time as the teams work out how they deal with any gaps. It's also possible that Google find some gaps on their side and have to resolve them before any transfer could actually happen.

Given the implications of service continuity if domains aren't transferred or operational, I can't imagine that they would ask customers to take some action. It creates a support nightmare with confused customers talking to support and then being unhappy they still took the wrong action when you ask them to approve the transfer.

I feel like this is one of the things that Gergely has sensationalized recently to drive attention. This started with a bunch of tweets which amounted to "why wasn't I told about this immediately". I suspect that this decision was made at exec levels with the lower levels asked to work out the details which obviously resulted in a delay. As a Google Domains customer, this wasn't particularly problematic. It's just a big company getting its ducks in a row which takes time.

It's self-evident that acquisitions can happen and that data will be transferred as a result. Most most attention is typically on other aspects of how Google handles data and this seems like an attempt to latch onto that.

I personally feel better about basic data security and processing under Google than I would under a company like Squarespace. I know Google have faced nation state attackers so they've got some security chops. I feel that they'll enforce reasonable contractual requirements on the purchaser, but those won't override Google being a safer bet with the basics.

>> However, that leaves a lot of C code that you can't talk to anymore because the C code requires the old Python FFI. I think this is where the main problem lies.

This is exactly the problem, but people have a hard time grasping this because most people interacting with Python have no understanding of how C code interacts with Python, or don't understand the C module ecosystem. I'm not sure if the Python community has a good accounting of this either because I don't recall seeing much quantitative analysis of how many modules would need to be updated etc.

This would help compare with the Python 2 to 3 conversion efforts. Even then, the site listing (shaming?) popular modules with compatibility made a mid-to-late appearance in the process of killing Python 2. Quantification of module updates is obvious thing to have from the get-go for anyone looking to follow through on removing the GIL, but it's not a fun task.

This feels like it's playing out as I expected. I followed Python, and the Python community, really closely from 2008-2016 when there were tons of relatively small scale experiments happening. This all happened organically to a large extent and there was no one coordinating a grand vision. It seems like we have a continuation of this giving rise to the concern that there is some battle.

I suspect there will be some butting of heads for a while before they work things out after seeing how the community reacts. All of this could be handled better with some thoughtful proactive engagement, but that's not really how things operate and there is no one to really enforce it.

You can't have in-person conversations when the community is supporting someone with a rare disease. However, many conversations don't fit into this class, and some would be better happening in-person. All of these things are true, so you still need Reddit alternatives.

I'm not sure what time period you are referring to. In the UK in the 90s you would call up Dell and talk to them about pricing and specs after seeing an ad like those on https://www.pcmag.com/news/the-golden-age-of-dell-computers.

The customer service experience at the time was great compared to what you'd typically deal with in the UK. I was the person buying computers for my parents' business, my parents' friends, and some of my friends, all through my parent's business . The reps were probably a little confused because they had repeat orders from the same "customer", but knew they were also dealing with a teenager that had done their research. This yielded some fun conversations and I always felt that they wanted to be competitive with their pricing.

Unfortunately, this all changed towards the end of the 90s as PC manufacturers cut costs, moved to the web, and outsourced.

Writing Win32 programs in assembly was a niche in the late-90s. This post inspired me to do some googling for a project I was familiar with back then and discovered the author has brought it back to life at https://github.com/ThomasJaeger/VisualMASM.

According to friends reading is still fairly prevalent for Windows and other products at Microsoft. Kind of a requirement to succeed in jobs with a C/C++ product where you might only have memory dumps to debug. It's also expected to some extent if you are a performance guru in some areas.

I haven't looked beyond your example page, but analytics (justifying internal tooling) and compliance (mitigating bad actors) features are required to gain entry in companies who would pay a lot for your product. You can get far without these features, but a lot of companies willing to pay money to automate away human involvement need to meet compliance levels you likely haven't experienced based on the description above.

There is zero chance these customers would let an engineer SSH into a production environment either when they have compliance requirements. Either it'll be some just-in-time access via a jumphost, or production changes need to be scripted separately. I would think about some kind of internal tools API offering. You deploy that onsite and all of these tools work through it. You then start more lock-in. If your current tools just hit internal APIs that exist anyway then your tool is easily replaced.

It's hard to evaluate your experience without knowing more about you and the podcasts you subscribed to. Can you share more?

In my experience, repeat listening is going to depend on the content and style of the podcast. Some will naturally bring you along while others can't generate great output consistently. The pattern I see is guest participation in the great episodes. Guests can't sustain a podcast unless there is a strong pipeline.

A podcast like Accidental Tech Podcast is consistently great for the fanbase, to the point where they'll pay for unedited versions. There have only been a few guests over the years and it's completely sustained by the creators. The Rest is History is completely sustained by the creators, but guests are regularly included. Sometimes I'm disappointed when they have a guest. CoRecursive depends on guests and has much more variability for me.

In halls or an apartment? I applied for Weston Hall when I was at UMIST, but ended up in Fallowfield :( The most important thing that Manchester did was open my mind having grown up in the the bigoted hinterlands of Northern Ireland.

I hadn't thought about the rugby club in my hometown for years. I looked it up recently and some YouTuber had sponsored them [1] for stadium naming rights [2]. It's not a surprise how it ended.

[1] https://en.wikipedia.org/wiki/City_of_Derry_R.F.C. [2] https://www.newsletter.co.uk/news/mini-ladd-youtube-sensatio...

Why do things in two places when you can do it all in one place? This isn't limited to computers, but unless you are getting specific benefits, it isn't wise to continue with a SPA approach.

We had the same and worse problems with "thick clients" that came before the web grew. With the right requirements, team, tools etc., you could sometimes build great apps. This was incredibly difficult and the number of great apps was relatively small. Building with earlier server-side web tech, like PHP, isolated everything on the server and it was easier to iterate well than with the "thick clients" model.

SPA reinvents "thick clients" to some degree and brings back many of the complications. No one should claim you can't build a great SPA, or that they have few advantages, but the probability of achieving success is frequently lower. Frameworks try to mitigate these concerns, but you are still only moving a closing some of the gaps and the probability of failure remains higher. Depending on the app you can move the success metrics, but we often end up fudging on items like performance.

We get to a point where there is current model is fraying and energy builds to replace it with something else. We end up going back to old techniques, but occasionally we learn from what was done before.

I find that it's surprisingly rare for people with 1-2 years of experience to be able to give an accurate overview of the last 10 years of web development. A better understanding of this history can help with avoiding (or targeting) problems old timers have encountered and complain about in comments.

Reddit was using Cassandra in 2010 (https://www.reddit.com/r/programming/comments/bcqhi/reddits_...). The experience was mentioned on HN at https://news.ycombinator.com/item?id=21694461. I expect that they started with an RDBMS and made various moves over the years.

>> Meanwhile, an enterprise running hundreds or even thousands of mac OS devices is something I've never heard of.

Your experience doesn't match with reality. There are multiple sources available describing the growth in macOS usage. One that's quoted in news reports, but hidden behind a paywall, is an IDC report from 2021[1].

It describes macOS penetration at ~23% in 2020 up 6% from 2019. The is supported by descriptions of the impact on enterprise end-user computing management teams that historically have only supported Windows. You can even look at the growth of Intune, and the breadth of acquisitions by Microsoft, to see that Microsoft is very likely supporting 1000s of mac devices.

An important element of how we got here is mobile. Windows had made huge investments in configuration management while OS X was an oddball. Managing it required a different set of tools. iOS and Android adoption in many enterprises caused an end run around the end-user computing gatekeepers from 2007-2012 with a proliferation in MDM solutions.

This eventually led to standardization of so-called "modern" configuration management API/interfaces/tools. The door was opened to more Mac adoption through Apple Business Manager while admins had already adopted modern management tools that covered Windows and mobile.

This doesn't discount the challenge with some users needing to use legacy Windows software. Once upon a time this was a strong moat. For years, IT have been under pressure to make this work on mobile (where feasible) which has cut down the blockers on macOS or Linux usage.

[1] https://www.idc.com/research/viewtoc.jsp?containerId=US46965...

There are also many variations on the contractor relationship that are important. Some contractors are hired through staff augmentation companies while others work through their own company.

Working through your own company is a much better arrangement, but harder to get setup. You'll have more control over rates and have the opportunity to get more work.

This all depends on having a relationship with someone with some kind of budgetary control and relationship with procurement. If procurement can get a better deal working directly with your company then it's normally possible to work something out. This is a good reason to build relationships with the "highly political" people that technical-types normally eschew.

Can archive box aggregate content "bookmarked" in different places?

I want a tool that will pull saved items on Reddit, favorite posts on HN, etc. in addition to bookmarks posted to pinboard.in to a single place. In many ways, the share functionality in iOS allows me to get all URLs into a single place, but this doesn't help on desktop.

I know this isn't necessarily and easy task, if APIs aren't available. I'd be OK with a client component or browser extension, if it was open source and self-hostable.

>> When did a lot of software devs stop caring?

I'm not sure the devs stopped caring as much as the powers at be. Software development has become more commoditized than we want to believe. Devs following an agile workflow with every intent of performing multiple rounds of optimization find that the product gets shipped as soon as it approximates the thing that had been conceived originally.

It doesn't look like an immediate failure, so the less that leadership takes from it is frequently that the level of maturity they shipped is safe. The cycle continues and eventually folks lower down succumb to this shipping pattern. The only things that get them to optimize is competition that successfully drive home their win was due to performance. This doesn't always lead to optimizations when you are an incumbent who can still close more feature gaps because those often result in higher sales and revenue.